Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: [rfc] Clarify shared library warning
Date: Tue, 10 Oct 2006 14:52:00 -0000	[thread overview]
Message-ID: <20061010145213.GA20993@nevyn.them.org> (raw)

This function, added recently by Alex, just saved me hours.  I was looking
back at an old bug report, and some inexplicable symbols that seemed to
start in the middle of functions.  And right there was a message from GDB,
not present last time I looked at the testcase:

warning: .dynamic section for "/lib/libc.so.6" is not at the expected
address

The tarball that went with the core dump had the wrong libraries in it.
No wonder it didn't work.

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

-- 
Daniel Jacobowitz
CodeSourcery

2006-10-10  Daniel Jacobowitz  <dan@codesourcery.com>

	* solib-svr4.c (LM_ADDR_CHECK): Suggest shared library mismatch.

Index: solib-svr4.c
===================================================================
RCS file: /cvs/src/src/gdb/solib-svr4.c,v
retrieving revision 1.58
diff -u -p -r1.58 solib-svr4.c
--- solib-svr4.c	18 May 2006 20:38:56 -0000	1.58
+++ solib-svr4.c	10 Oct 2006 14:47:59 -0000
@@ -221,6 +221,11 @@ LM_ADDR_CHECK (struct so_list *so, bfd *
 	      warning (_("difference appears to be caused by prelink, "
 			 "adjusting expectations"));
 	    }
+	  else
+	    {
+	      warning (_("the wrong version of the shared library may "
+			 "have been found"));
+	    }
 	}
 
     set_addr:


             reply	other threads:[~2006-10-10 14:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 14:52 Daniel Jacobowitz [this message]
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
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=20061010145213.GA20993@nevyn.them.org \
    --to=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