From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org
Subject: Re: [rfc] Clarify shared library warning
Date: Wed, 11 Oct 2006 20:51:00 -0000 [thread overview]
Message-ID: <20061011205123.GA9760@nevyn.them.org> (raw)
In-Reply-To: <17946.82.92.89.47.1160599757.squirrel@webmail.xs4all.nl>
On Wed, Oct 11, 2006 at 10:49:17PM +0200, Mark Kettenis wrote:
> > On Wed, Oct 11, 2006 at 10:32:25PM +0200, Mark Kettenis wrote:
> > > I prefer Eli's version. I also think that if further explanation
> > > beyond Eli's version is required the proper place really is the manual.
> >
> > Would you all be happy with this compromise?
> >
> > warning: .dynamic section for "/lib/libc.so.6" is not at the expected
> > address (wrong shared library found?)
>
> Ah, I must have been unclear. This message is fine with me. It's just
> messages that are significantly longer than that, that I want to ban
> to the manual.
I agree; my original version was too wordy. I'll have to move the
warnings around to get this, but it will be easy, and I agree that the
concise warning is more useful.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-11 20:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 14:52 Daniel Jacobowitz
2006-10-10 21:28 ` Eli Zaretskii
2006-10-10 21:34 ` Joel Brobecker
2006-10-11 13:38 ` Daniel Jacobowitz
2006-10-11 16:09 ` Joel Brobecker
2006-10-11 20:32 ` Mark Kettenis
2006-10-11 20:39 ` Daniel Jacobowitz
2006-10-11 20:49 ` Mark Kettenis
2006-10-11 20:51 ` Daniel Jacobowitz [this message]
2006-10-12 4:29 ` Eli Zaretskii
2006-10-12 5:52 ` Joel Brobecker
2006-10-12 6:55 ` Eli Zaretskii
2006-10-12 14:39 ` Joel Brobecker
2006-10-12 14:46 ` Andreas Schwab
2006-10-13 15:10 ` Eli Zaretskii
2006-10-13 15:18 ` Daniel Jacobowitz
2006-10-17 20:53 ` Daniel Jacobowitz
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=20061011205123.GA9760@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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