This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Missing separate debuginfos
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>, Debug List <debug-list at redhat dot com>, nt_mahmood at yahoo dot com, "gdb\ at sourceware dot org" <gdb at sourceware dot org>
- Date: Fri, 15 Mar 2013 09:26:14 -0600
- Subject: Re: Missing separate debuginfos
- References: <1361295973.55844.YahooMailNeo@web163002.mail.bf1.yahoo.com> <m3a9r0m57o.fsf@redhat.com> <5123E23D.9010007@redhat.com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Debug info for packages used by the program missing. Install with:
Pedro> debuginfo-install
Pedro> But of course that may well just be me.
Maybe be even wordier, like
Some debug info for packages used by the program is missing. You can
install this with:
debuginfo-install package-1 \
package-2 \
package-3
Once the packages are installed, you can use them in the current gdb
with:
nosharedlibrary
sharedlibrary .*
Future invocations of gdb will pick them up automatically.
Of course then you get into pagination, especially if you have a ton of
uninstalled debug packages.
We could trim this down the second time it is printed.
Maybe it would be nice if debuginfo-install were a gdb command.
Then it could do the sharedlibrary dance for the user, without needing
nosharedlibrary.
The "nosharedlibrary" thing is also hard to figure out.
See http://sourceware.org/bugzilla/show_bug.cgi?id=12794
and http://sourceware.org/bugzilla/show_bug.cgi?id=14479
This could definitely use an enhancement.
Tom