Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 362958

Summary: NullPointerException when "stop on startup at" refers to a missing method
Product: [Tools] CDT Reporter: David Beswick <dlbeswick>
Component: cdt-debugAssignee: cdt-debug-inbox <cdt-debug-inbox>
Status: NEW --- QA Contact: Jonah Graham <jonah>
Severity: normal    
Priority: P3 CC: cdtdoug, malaperle, pawel.1.piech
Version: 8.0.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

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.