|
|
|
| Re: debugger not stopping at breakpoints [message #638768 is a reply to message #638695] |
Fri, 12 November 2010 14:25   |
 Marc Khouzam
Messages: 357
Registered: July 2009 |
Senior Member |
|
|
| No Real Name wrote on Fri, 12 November 2010 04:04 | It does give an error:
364,140 14-break-insert <absolute-path-to-the-file>/mysingleton.h:166
364,219 14^error,msg="No source file named <absolute-path-to-the-file>/mysingle\
ton.h."
I am unsure why the backslash is inserted, could that be the problem? Otherwise, the file where it tries to insert the breakpoint exists (tested with ls).
When I start gdb in the console, and set the breakpoint with "break", I get:
Make breakpoint pending on future shared library load? (y or [n])
But when I say "y", everything works. Could that be connected to the problem?
Thanks!
|
The backslash is just to break the line in the output. That is ok.
The problem is that when you set the breakpoint (when eclipse does), the file in question has not been loaded. Seems to be a library. Handling this properly is something that was missed for CDT 7.0 but has been fixed for the upcoming release. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=248595
Until then, for this case, you will have to use the old debugger integration, which has this feature. In your launch window, at the bottom you will see a hyperlink saying "Using GDB (DSF) Create process launcher - Select other..."
Click on that, and choose "Standard create process launcher", then make sure all attributes are correct and launch as before.
Marc
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02946 seconds
] 
Search
Help
Register
Login
Home
