This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/13870] New: gdb doesn't find source file withabsolute path after the first try (second try succeeds)
- From: "andreas at pietzowski dot de" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 19 Mar 2012 22:00:55 +0000
- Subject: [Bug breakpoints/13870] New: gdb doesn't find source file withabsolute path after the first try (second try succeeds)
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13870
Bug #: 13870
Summary: gdb doesn't find source file with absolute path after
the first try (second try succeeds)
Product: gdb
Version: 7.3
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned@sourceware.org
ReportedBy: andreas@pietzowski.de
Classification: Unclassified
I have a problem with my KDevelop/qmake project debugging with absolute files
(KDevelop uses absolute paths for debugging). When I start gdb from command
line I can reproduce why KDevelop ist breaking at the breakpoints I set in the
IDE.
To explain it better, here is exactly what I did:
$ gdb ./myapplication
(gdb) break /absolute/file/path/to/main.cpp:34
No source file named /absolute/file/path/to/main.cpp.
Make breakpoint pending on future shared library load? (y or [n]) n
(gdb) list
31 #include "blabla.h"
32
33 int main(int argc, char *argv[]) {
34 QApplication a( argc, argv );
(gdb) break /absolute/file/path/to/main.cpp:34
Breakpoint 1 at 0xC0FFEE: file relative/path/to/main.cpp, line 34.
(gdb) run
Breakpoint 1, main (argc=1, argv=0x7fffffffe108) at application/main.cpp:34
34 QApplication a( argc, argv );
Isn't that strange? Two times the same break command to gdb with different
results? Do you have any ideas why gdb first need the "list" command to detect
the correct file?
By the way: My project has about 1500 source files...
Thanks
Andreas
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.