Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Luis Machado <luisgpm@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle absence of DT_DEBUG while debugging ld.so
Date: Tue, 29 Jul 2008 02:27:00 -0000	[thread overview]
Message-ID: <20080729022723.GA6298@caradoc.them.org> (raw)
In-Reply-To: <1217289278.16935.23.camel@gargoyle>

On Mon, Jul 28, 2008 at 08:54:37PM -0300, Luis Machado wrote:
> 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.

I think this is a PIE-related problem.  It has nothing to do with
uninitialized, because we're just taking the symbol's
address; but the address you've got there looks wrong.  It's as if
ld.so was loaded at 0x0.  How did that happen?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-07-29  2:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 23:55 Luis Machado
2008-07-29  2:27 ` Daniel Jacobowitz [this message]
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=20080729022723.GA6298@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    /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