This is the mail archive of the
mailing list for the GDB project.
Re: gdb backtrace include library as well as symbol name
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Jon Grant <jg at jguk dot org>, gdb at sourceware dot org
- Date: Mon, 26 Sep 2011 08:36:01 -0700
- Subject: Re: gdb backtrace include library as well as symbol name
- References: <4E7FAB5E.email@example.com> <20110926063307.GA1031@host1.jankratochvil.net>
> > Is there a way to get the "bt" command to output the library or ELF
> > binary file that the symbol orginates in? Would be handy if this
> > could even be the default:
> Yes, this is common RFE. It was discussed in the thread:
> Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
I understood that thread as being something slightly different.
But what's being asked here is that the name of the exe being
debugged be printed for symbols in the main exe. This is the only
time as far as I known when the name of the objfile is not
printed, so I think that the current output is fine.
There has been a project of decorated backtraces, which allows
a user to enhance them via Python. Have you looked at this project?
Not sure if this project made it to the main repository, of if
it is still only in Archer, though.
> > #0 0xb7773424 in __kernel_vsyscall ()
> > #0 Doesn't show lib. I think this is glibc.
> It is Linux kernel provided [vdso], it has DWARF info.
To complete what Jan said, it is in memory, but does not have
a corresponding file.