From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: dje@google.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: too many "no debugging symbols found" messages from shared libs
Date: Tue, 11 Nov 2008 05:03:00 -0000 [thread overview]
Message-ID: <uwsfaq4vt.fsf@gnu.org> (raw)
In-Reply-To: <20081110204431.GA3771@caradoc.them.org>
> Date: Mon, 10 Nov 2008 15:44:31 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: dje@google.com, brobecker@adacore.com, gdb-patches@sourceware.org
>
> On Mon, Nov 10, 2008 at 10:23:39PM +0200, Eli Zaretskii wrote:
> > It's been a long day, and I'm no longer sure I understand whether what
> > you are saying is something different from what I said. Are you
> > saying that even if the user turns on the option to print this for
> > each shared library, we should not print that (or not have the
> > option)? I'm okay with having such an option off by default, but I
> > was asking to display a file name if the option is ON.
>
> I'm confused too - what option?
I thought the original patch came with a suggestion to add an option,
in case user wanted to see these messages.
next prev parent reply other threads:[~2008-11-11 4:11 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
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 [this message]
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=uwsfaq4vt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=drow@false.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