Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362958 - NullPointerException when "stop on startup at" refers to a missing method
Summary: NullPointerException when "stop on startup at" refers to a missing method
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 8.0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-04 22:29 EDT by David Beswick CLA
Modified: 2020-09-04 15:21 EDT (History)
3 users (show)

See Also:

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 David Beswick CLA 2011-11-04 22:29:42 EDT 
Build Identifier: M20110210-1200

I was using gdb to debug extension DLLs for an external process. I had "stop on startup at 'main'" checked accidentally, and it would cause a NullPointerException whenever I tried to start debugging. I'm guessing that it's because my project doesn't have a 'main' method. Unchecking the option fixed the issue.

Reproducible: Always

Steps to Reproduce:
1. Specify an external executable in the "C/C++ Application" debug configuration field.
2. Select "stop on startup at:..." and specify a non-existent function.
3. Start debugging.
Comment 1 Marc-André Laperle CLA 2012-05-02 12:50:11 EDT 
I can't reproduce this. Are you using GDB? Can you paste or attach the call stack related to the NPE? Thanks.