Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Handle absence of DT_DEBUG while debugging ld.so
Date: Mon, 28 Jul 2008 23:55:00 -0000	[thread overview]
Message-ID: <1217289278.16935.23.camel@gargoyle> (raw)

Hi folks,

When trying to debug ld.so, we may find that the DT_DEBUG entry in
the .dynamic section is missing, thus GDB tries to look for the _r_debug
minimal symbol, and eventually finds it. This works OK as long as the
_r_debug minimal symbol is correct and initialized.

In the case where GDB fetches an uninitialized _r_debug minimal symbol
and tries to access its address, we have a memory access error, just
like below:

(gdb) r
Starting program: /foo/lib/ld.so.1
Cannot access memory at address 0x2f648

Thus, we should guard this piece of code against uninitialized addresses
so that GDB can skip this entry and look for another (hopefully) valid
_r_debug symbol.

Tested against HEAD for ppc32/ppc64 with no regressions. OK?

Regards,
Luis

---
2008-07-28  Luis Machado  <luisgpm@br.ibm.com>

	* solib-svr4.c (elf_locate_base): Check if msymbol's
	address is valid.

Index: gdb/solib-svr4.c
===================================================================
--- gdb.orig/solib-svr4.c	2008-07-28 14:35:20.000000000 -0700
+++ gdb/solib-svr4.c	2008-07-28 16:11:42.000000000 -0700
@@ -508,9 +508,14 @@
     return dyn_ptr;
 
   /* This may be a static executable.  Look for the symbol
-     conventionally named _r_debug, as a last resort.  */
+     conventionally named _r_debug, as a last resort and check if
+     the address contained in the minimal symbol is valid before
+     proceeding.  */
   msymbol = lookup_minimal_symbol ("_r_debug", NULL, symfile_objfile);
-  if (msymbol != NULL)
+  if (msymbol != NULL
+      && !target_read_memory (SYMBOL_VALUE_ADDRESS (msymbol),
+			      (gdb_byte *)&dyn_ptr,
+			      TYPE_LENGTH (builtin_type_void_data_ptr)))
     return SYMBOL_VALUE_ADDRESS (msymbol);
 
   /* DT_DEBUG entry not found.  */



             reply	other threads:[~2008-07-28 23:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 23:55 Luis Machado [this message]
2008-07-29  2:27 ` Daniel Jacobowitz
2008-07-29  2:57   ` Luis Machado
2008-07-29  3:03     ` Luis Machado
2008-07-29 12:13     ` Daniel Jacobowitz
2008-07-29 12:46       ` Luis Machado
2008-08-12 18:16         ` Luis Machado
2008-09-05 18:31           ` Luis Machado
2008-07-29 12:55       ` Pedro Alves

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=1217289278.16935.23.camel@gargoyle \
    --to=luisgpm@linux.vnet.ibm.com \
    --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