Version: 3.0.90-CVS (using KDE 3.2.1, compiled sources) Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-99-default Project: Simple C++ Template class foo, sources in files: src/foo.h src/foo_impl.h Starting the debugger to debug the debug-enabled executable (default debug-config setup): -- gdb /home/daniel/cvs/sibsim3/debug/src/sibsim3 -fullname -nx -quiet (gdb) set edit off (gdb) set confirm off (gdb) set print static-members off (gdb) tty /dev/pts/7 (gdb) set width 0 (gdb) set height 0 (gdb) set stop-on 1 (gdb) handle SIG32 pass nostop noprint (gdb) handle SIG43 pass nostop noprint (gdb) set print asm-demangle on (gdb) set output-radix 10 (gdb) cd /home/daniel/cvs/sibsim3/debug/src (gdb) break node_impl.h:36 No source file named node_impl.h. -- Changing the directory back to -- (gdb) cd /home/daniel/cvs/sibsim3/src -- solves this issue, the files are found again, breakpoints are set. Drawback: the path is reset each start/stop cycle.
Additional note: When breaking at main(): gdb /home/daniel/cvs/sibsim3/debug/src/sibsim3 -fullname -nx -quiet (gdb) set edit off (gdb) set confirm off (gdb) set print static-members off (gdb) tty /dev/pts/7 (gdb) set width 0 (gdb) set height 0 (gdb) set stop-on 1 (gdb) handle SIG32 pass nostop noprint (gdb) handle SIG43 pass nostop noprint (gdb) set print asm-demangle on (gdb) set output-radix 10 (gdb) cd /home/daniel/cvs/sibsim3/debug/src (gdb) break node_impl.h:36 No source file named node_impl.h. <<< [same error as before] (gdb) break sibsim3.cpp:55 Breakpoint 1 at 0x8048978: file /home/daniel/cvs/sibsim3/src/sibsim3.cpp, line 55. <<< [ main() ] Stopped due to shared library event (gdb) break node_impl.h:36 Breakpoint 2 at 0x8048dfe: file node_impl.h, line 36. <<< [now the breakpoint is set]
Created attachment 9087 [details] Testcase Exactly the same behaviour in kdevelop-3.1.91, KDE-3.3.91, CVS 050113. To reproduce: - Set breakpoint at mytemplate_impl.h:33, run debugger -> can't set breakpoint. - Set breakpoint at mytemplate_impl.h:33 AND main(), run debugger -> breakpoint is set, execution stops
Suggest closing this as WONTFIX - it seems to be an GDB issue. GDB behaves the same if I run this test standalone in a konsole. Could have tested this beforehand - sry about the fuss.
Heh. That was my thought when you added the testcase the other day.. "I wonder if gdb can do that..?". Never got around to testing it.. :) I'm closing as INVALID.