From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: too many "no debugging symbols found" messages from shared libs
Date: Sat, 08 Nov 2008 09:15:00 -0000 [thread overview]
Message-ID: <ufxm2shon.fsf@gnu.org> (raw)
In-Reply-To: <e394668d0811071444m14cce80bgc554d83c699e9773@mail.gmail.com>
> Date: Fri, 7 Nov 2008 14:44:15 -0800
> From: Doug Evans <dje@google.com>
>
> On Wed, Oct 29, 2008 at 8:04 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> >> An alternative patch would be to at least include the file name
> >> in the message. But if we do want to print this message for shared-libs
> >> why should it be predicated on whether the main program is stripped or not?
> >
> > I have to agree that the current situation is confusing. Before looking
> > at the patch itself, the first thing is to agree on what the debugger
> > should be doing at the user level. Perhaps there was a logic behind
> > the current implementation that we're not seeing yet.
> >
> > IMO, a shared library without debugging symbol is a common and perfectly
> > normal occurrence, and thus does not deserve a warning - at least not
> > by default, particularly when the number of SOs becomes large. So I
> > would have to agree with the suggested patch.
> >
> > What do others think?
>
> ping.
I think we should apply Doug's patch _and_ make the other change he
suggests as the "alternative" one, i.e. to print the file name as part
of the message for shared libraries.
next prev parent reply other threads:[~2008-11-08 9:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 21:35 Doug Evans
2008-10-30 5:19 ` Joel Brobecker
2008-11-07 22:45 ` Doug Evans
2008-11-08 9:15 ` Eli Zaretskii [this message]
2008-11-10 16:46 ` Daniel Jacobowitz
2008-11-10 18:32 ` Joel Brobecker
2008-11-10 20:33 ` Eli Zaretskii
2008-11-10 20:51 ` Daniel Jacobowitz
2008-11-11 5:03 ` Eli Zaretskii
2008-11-11 5:34 ` Daniel Jacobowitz
2008-11-21 18:46 ` Doug Evans
2008-11-21 19:16 ` Eli Zaretskii
2008-11-21 19:24 Mark Kettenis
2008-11-21 22:08 ` Eli Zaretskii
2008-11-22 4:43 ` Doug Evans
2008-11-22 6:38 ` Eli Zaretskii
2008-11-22 16:49 Mark Kettenis
2008-11-22 17:49 ` Doug Evans
2008-11-22 21:41 ` Eli Zaretskii
2008-11-24 3:23 ` Paul Pluzhnikov
2008-11-24 16:54 ` Eli Zaretskii
2008-11-24 19:42 ` Doug Evans
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=ufxm2shon.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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