This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug backtrace/13849] New: gdb unable to find file and lineno inbacktrace, even though break file:line works and finds the same address
- From: "navinkumar+bugs at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 14 Mar 2012 20:23:49 +0000
- Subject: [Bug backtrace/13849] New: gdb unable to find file and lineno inbacktrace, even though break file:line works and finds the same address
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13849
Bug #: 13849
Summary: gdb unable to find file and lineno in backtrace, even
though break file:line works and finds the same
address
Product: gdb
Version: 7.4
Status: NEW
Severity: critical
Priority: P2
Component: backtrace
AssignedTo: unassigned@sourceware.org
ReportedBy: navinkumar+bugs@gmail.com
Classification: Unclassified
Created attachment 6288
--> http://sourceware.org/bugzilla/attachment.cgi?id=6288
gdb output showing "break file:line" succeeds and "list *address" fails
Analyzing a core file, "where" displays the backtrace, and correctly resolves
addresses to symbol names, but is unable to find file:lineno for many of the
frames and fails to display any other debug info (e.g. local variables,
argument values, etc.) for these frames.
The binary is compiled with gcc 4.5.3 using -O0 -g3 flags.
Curiously, "break file:lineno" works in gdb for these frames, and "info b"
lists the correct functions and addresess, but "list *(address)" to do the
reverse, using the exact same address "info b" shows, gives the error "No
source file for address".
This is affecting our ability to analyze our corefile and without knowing the
local variables and argument values we are unable to proceed diagnosing our
application.
--
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.