Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Clarify shared library warning
Date: Tue, 10 Oct 2006 21:28:00 -0000	[thread overview]
Message-ID: <uejtfkgia.fsf@gnu.org> (raw)
In-Reply-To: <20061010145213.GA20993@nevyn.them.org> (message from Daniel 	Jacobowitz on Tue, 10 Oct 2006 10:52:13 -0400)

> Date: Tue, 10 Oct 2006 10:52:13 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> But this warning isn't very self-explanatory.  I was thinking something
> like the below, in addition.  How does this sound?
> 
> 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?)


  reply	other threads:[~2006-10-10 21:28 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 [this message]
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
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=uejtfkgia.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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