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 258467 - Debugger does not launch
Summary: Debugger does not launch
Status: RESOLVED INCOMPLETE
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 8.1
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Assignee: henk89
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-21 13:39 UTC by chakie
Modified: 2016-06-16 12:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot showing how the debugger fails (180.96 KB, image/png)
2016-03-21 13:39 UTC, chakie
Details
Screenshot showing the CLang toolchain options and debugger (248.40 KB, image/png)
2016-03-21 13:40 UTC, chakie
Details
Screenshot showing selected toolchain (172.05 KB, image/png)
2016-03-21 13:41 UTC, chakie
Details

Note You need to log in before you can comment on or make changes to this bug.
Description chakie 2016-03-21 13:39:07 UTC
I wanted to debug my project. Clicked on "Debug Project". The debugger does not launch, but exits with error code 0. Perhaps it requires some extra command line options? The debugger is set up in the preferences with a valid path. See screenshots for the config cruft.
Comment 1 chakie 2016-03-21 13:39:48 UTC
Created attachment 158949 [details]
Screenshot showing how the debugger fails
Comment 2 chakie 2016-03-21 13:40:35 UTC
Created attachment 158950 [details]
Screenshot showing the CLang toolchain options and debugger
Comment 3 chakie 2016-03-21 13:41:11 UTC
Created attachment 158951 [details]
Screenshot showing selected toolchain
Comment 4 chakie 2016-03-21 13:42:00 UTC
The failure popup seems to indicate it tries to use GDB? Sounds weird, as GDB is not set up for this toolchain (nor any other toolchain), but LLDB.
Comment 5 henk89 2016-03-21 16:16:24 UTC
GDB and LLDM-MI use almost the same command set. You may get the additional info on how to set LLDB-MI up from the issue #236801.