From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <dje@google.com>,
brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: too many "no debugging symbols found" messages from shared libs
Date: Mon, 10 Nov 2008 16:46:00 -0000 [thread overview]
Message-ID: <20081110144528.GC12962@caradoc.them.org> (raw)
In-Reply-To: <ufxm2shon.fsf@gnu.org>
On Sat, Nov 08, 2008 at 11:14:32AM +0200, Eli Zaretskii wrote:
> 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.
Even a stripped shared library has more symbols than a stripped
executable, because more of the library will be in externally visible
entry points. I agree with Joel - having a message print out for each
shared library is annoying when you have dozens of shared libraries
(common especially on Windows). So how about we print out "(no
debugging symbols for my/binary.exe)" and not print out anything for
shared libraries?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-11-10 14:46 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
2008-11-10 16:46 ` Daniel Jacobowitz [this message]
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=20081110144528.GC12962@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--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