From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Debug List <debug-list@redhat.com>,
nt_mahmood@yahoo.com,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Missing separate debuginfos
Date: Fri, 15 Mar 2013 15:26:00 -0000 [thread overview]
Message-ID: <874ngc3crt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5123E23D.9010007@redhat.com> (Pedro Alves's message of "Tue, 19 Feb 2013 20:36:13 +0000")
>>>>> "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
next prev parent reply other threads:[~2013-03-15 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 17:46 Mahmood Naderan
2013-02-19 20:14 ` Sergio Durigan Junior
2013-02-19 20:36 ` Pedro Alves
2013-03-15 15:26 ` Tom Tromey [this message]
2013-03-15 15:29 ` [debug-list] " Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874ngc3crt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=debug-list@redhat.com \
--cc=gdb@sourceware.org \
--cc=nt_mahmood@yahoo.com \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox