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 193424 - Problem starting debugger (CPP on OSX)
Summary: Problem starting debugger (CPP on OSX)
Status: RESOLVED DUPLICATE of bug 193427
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-15 08:36 UTC by mortennobel
Modified: 2010-12-20 15:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Netbeans log (42.15 KB, application/octet-stream)
2010-12-15 08:37 UTC, mortennobel 		Details
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 mortennobel 2010-12-15 08:36:34 UTC 
When I start the debugger on any CPP project on OSX the exception dialog appears for a second - then it disappears again and the debugger start up correct. I'm unable to submit this from the exception dialog.

I can see the exception on the messages.log (see attached file).

So there is actually two problems:
1. Some exception happens when starting the C++ debugger
2. Something shuts down the exception dialog

Product Version = NetBeans IDE Dev (Build 201012150001)
Operating System = Mac OS X version 10.6.5 running on x86_64
Java; VM; Vendor = 1.6.0_22
Runtime = Java HotSpot(TM) 64-Bit Server VM 17.1-b03-307
Comment 1 mortennobel 2010-12-15 08:37:35 UTC 
Created attachment 104105 [details]
Netbeans log
Comment 2 mortennobel 2010-12-15 09:29:57 UTC 
I managed to do the error report while the CPU was busy doing other things:
http://statistics.netbeans.org/analytics/exception.do?id=453697
Comment 3 Thomas Preisler 2010-12-15 16:58:23 UTC 
Please see https://netbeans.org/bugzilla/show_bug.cgi?id=193269.  mortennobel thinks there may be a connection.
Comment 4 Marian Mirilovic 2010-12-20 15:25:37 UTC 

*** This bug has been marked as a duplicate of bug 193427 ***