User forums > Help
Debugger can't find project files
280Z28:
--- Quote from: killerbot on December 31, 2005, 10:13:49 am ---Yes, the breakpoint works , that's for sure. But strange someone is saying our file is not found -> confusing.
Debuggers log coming up.
--- End quote ---
Well GDB will always spit out that message before a pending breakpoint. Maybe the debugger plugin should recognize this output from GDB:
--- Code: ---> 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.
--- End code ---
and transparently show just this to the user:
--- Code: ---Breakpoint 1 (D:/Devel/codeblocks/src/sdk/editormanager.cpp:2340) pending.
--- End code ---
killerbot:
Command-line: C:\Program Files\CodeBlocks\bin\gdb.exe -nx -fullname -args devel/codeblocks.exe --debug-log --no-check-associations -ns
Working dir : C:\cb_snap\svn\src\
> set prompt (gdb)
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...
(gdb) (gdb)
> set confirm off
(gdb)
> set width 0
(gdb)
> set height 0
(gdb)
> set breakpoint pending on
(gdb)
> set print asm-demangle on
(gdb)
> set disassembly-flavor intel
(gdb)
> cd devel
(gdb)
> directory C:/cb_snap/svn/src/
(gdb)
> delete
(gdb)
> break C:/cb_snap/svn/src/sdk/projectfileoptionsdlg.cpp:97
No source file named C:/cb_snap/svn/src/sdk/projectfileoptionsdlg.cpp.
Breakpoint 1 (C:/cb_snap/svn/src/sdk/projectfileoptionsdlg.cpp:97) pending.
(gdb)
> run
Breakpoint 2 at 0x6057736a: file sdk/projectfileoptionsdlg.cpp, line 97.
Pending breakpoint "C:/cb_snap/svn/src/sdk/projectfileoptionsdlg.cpp:97" resolved
This is the output, strange I have 2 breakpoints now ??
killerbot:
I just tried it out also on a little project (just a main.cpp), there it is OK.
So it seems it the sources are in another dll or something else (what's else), it happens.
So if it is a bug in GDB, maybe Sam's suggestion to filter it out is a good idea (less confusion for the user), since user perception is an dangerous thing. If you tell clients well, it 's complaining but it works fine, they don't trust you. ;-)
Mr. Awesome:
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):
--- Code: ---> 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
--- End code ---
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.
yop:
--- Quote from: killerbot on December 31, 2005, 10:28:07 am ---So if it is a bug in GDB, maybe Sam's suggestion to filter it out is a good idea (less confusion for the user), since user perception is an dangerous thing. If you tell clients well, it 's complaining but it works fine, they don't trust you. ;-)
--- End quote ---
Sorry I won't agree on that, IMHO the gdb user should know what the debuger outputs (if you present him with this option) and have the output intact, or at least give him the option to view it (like the debugger output cb has now). Also secondly how can you filter out a so commonly used message (No source file...) from gdb?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version