From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "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:32:00 -0000 [thread overview]
Message-ID: <9704.82.92.89.47.1160598745.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20061011133756.GB25164@nevyn.them.org>
> On Tue, Oct 10, 2006 at 02:34:38PM -0700, Joel Brobecker wrote:
> > > > warning: .dynamic section for "/lib/libc.so.6" is not at the
> > expected
> > > > address
> > > > warning: the wrong version of the shared library may have been found
> > >
> > > Such a change is a good idea, I think.
> > >
> > > We could make it shorter, though:
> > >
> > > warning: .dynamic section for "/lib/libc.so.6" is not at the
> > expected
> > > address (wrong version of the shared library?)
> >
> > I like the change too, but I prefer Daniel's version. I find it much
> > clearer.
>
> Actually, I like Eli's version better, myself. If you find the longer
> one clearer, could you try to explain why?
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.
Mark
next prev parent reply other threads:[~2006-10-11 20:32 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 [this message]
2006-10-11 20:39 ` Daniel Jacobowitz
2006-10-11 20:49 ` Mark Kettenis
2006-10-11 20:51 ` Daniel Jacobowitz
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=9704.82.92.89.47.1160598745.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.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