From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Debug List <debug-list@redhat.com>,
nt_mahmood@yahoo.com,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Missing separate debuginfos
Date: Tue, 19 Feb 2013 20:36:00 -0000 [thread overview]
Message-ID: <5123E23D.9010007@redhat.com> (raw)
In-Reply-To: <m3a9r0m57o.fsf@redhat.com>
On 02/19/2013 08:14 PM, Sergio Durigan Junior wrote:
> On Tuesday, February 19 2013, Mahmood Naderan wrote:
>
>> > What is the meaning of this message I see in gdb?
>> >
>> > Loaded symbols for /usr/lib64/libstdc++.so.6
>> > 0x00000037d6c0f3cb in raise () from /lib64/libpthread.so.0
>> > Missing separate debuginfos, use: debuginfo-install
> It means you don't have the debug information for these specific
> packages/versions. Unless you want to debug them, you don't really need
> to worry. If you ever want to debug them, you can run the command
> suggested.
A bit off topic for this list, but I've thought before that
message isn't as clear as it could be.
> Missing separate debuginfos, use: debuginfo-install
I think we could drop "separate", as it is an implementation
detail that shouldn't matter to the user. "debuginfos" being
plural reads a bit weird to me. I think this would be a bit
clearer:
Debug info for packages used by the program missing. Install with: debuginfo-install
But of course that may well just be me.
--
Pedro Alves
next prev parent reply other threads:[~2013-02-19 20:36 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 [this message]
2013-03-15 15:26 ` Tom Tromey
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=5123E23D.9010007@redhat.com \
--to=palves@redhat.com \
--cc=debug-list@redhat.com \
--cc=gdb@sourceware.org \
--cc=nt_mahmood@yahoo.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