OOhhh that's what it does. It can resolve pending breakpoints as they are encountered. You should see a "resolved" message when it is found.
GDB 5.x does not support pending breakpoints. That's why you need 6.3 :)
> break D:/Devel/codeblocks/src/sdk/editormanager.cpp:2340
No source file named D:/Devel/codeblocks/src/sdk/editormanager.cpp.
Breakpoint 1 (D:/Devel/codeblocks/src/sdk/editormanager.cpp:2340) pending.
(gdb)
> run
Breakpoint 2 at 0x618331f4: file sdk/editormanager.cpp, line 2340.
Pending breakpoint "D:/Devel/codeblocks/src/sdk/editormanager.cpp:2340" resolved
Yes, the breakpoint works , that's for sure. But strange someone is saying our file is not found -> confusing.
Debuggers log coming up.
Well GDB will always spit out that message before a pending breakpoint. Maybe the debugger plugin should recognize this output from GDB:
> break D:/Devel/codeblocks/src/sdk/editormanager.cpp:2340
No source file named D:/Devel/codeblocks/src/sdk/editormanager.cpp.
Breakpoint 1 (D:/Devel/codeblocks/src/sdk/editormanager.cpp:2340) pending.
and transparently show just this to the user:
Breakpoint 1 (D:/Devel/codeblocks/src/sdk/editormanager.cpp:2340) pending.
I'm getting kind of lost in this discussion, but here is the debug log that I'm getting (BTW I do have GDB 6.3):
> directory C:/C__PRO~1/AIGAME~1/Race/
> file Race.exe
> delete
> break Player.cpp:61
> set confirm off
> set disassembly-flavor intel
> run
pre-prompt
prompt
post-prompt
pre-prompt
prompt
post-prompt
breakpoints-invalid
error-begin
No source file named Player.cpp.
frames-invalid
pre-prompt
prompt
post-prompt
pre-prompt
prompt
post-prompt
error
pre-prompt
prompt
post-prompt
pre-prompt
prompt
post-prompt
pre-prompt
prompt
post-prompt
frames-invalid
<snip about 20 frames-invalid>
starting
frames-invalid
<snip maybe 60 frames-invalid>
exited 0
> quit
frames-invalid
stopped
pre-prompt
prompt
post-prompt
I don't know if this helps or what, like I said I'm lost. If you find a solution, please tell me what I need to do. Thanks for any help.