This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 73564 - Crashed program started Visual Studio
Summary: Crashed program started Visual Studio
Status: RESOLVED WONTFIX
Alias: None
Product: cnd
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: PC All
: P3 blocker (vote)
Assignee: _ gordonp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-14 00:59 UTC by _ gordonp
Modified: 2007-04-03 22:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ gordonp 2006-03-14 00:59:37 UTC 
Thomas just told me he forced a test app to crash and up popped a dialog
asking if he wanted to debug in Visual Studio. This should *not* be posted
from netbeans!!!
Comment 1 _ gordonp 2006-03-14 01:02:52 UTC 
This happened while running, not debugging.
Comment 2 Jesse Grodnik 2007-04-03 22:52:42 UTC 
This defect is an artifact of the Windows environment and the Visual Studio
Just-In-Time Debugging facility. It's not something that we can "fix" in the
NetBeans product. Through the Visual Studio Tools>Options>Debugging menu the
user can enable (and disable) the Just-In-Time Debugging. The effect of
enabling/disabling the facility is to set/reset a registry entry. To fix the
current problem the user needs to disable the JIT Debugging. A savvy user (with
administrator permissions) can also directly modify the registry entries (under
HKEY_LOCAL_MACHINE\Software\Microsoft\..) created by the Visual Studio.

When the Netbeans C/C++ Dev Pack debugger(s) provide an "attach" facility, we
may consider allowing the user to attach a specific available debugger to the
crashed program. This would require user input, since the automated JIT dialog
is not universally appreciated.