From: Daniel Jacobowitz <drow@false.org>
To: PAUL GILLIAM <pgilliam@us.ibm.com>
Cc: gdb@sources.redhat.com, sjmunroe@us.ibm.com
Subject: Re: breaks at thread create and delete fail on PPC64/Linux
Date: Mon, 28 Aug 2006 23:22:00 -0000 [thread overview]
Message-ID: <20060828232206.GA27059@nevyn.them.org> (raw)
In-Reply-To: <1156806903.5898.29.camel@dufur.beaverton.ibm.com>
On Mon, Aug 28, 2006 at 04:15:03PM -0700, PAUL GILLIAM wrote:
> 3) 'dereferencing' the function descriptor should give the
> actual address at which to set a breakpoint, but gives instead
> the offset within the "pthread" library where the breakpoint
> should be placed.
>
> The attached patch 'fixes' the problem by looking up the load address of the
> "pthread" library and adding that to the address from the PLT. This seems to
> do the trick, but THIS HAS ONLY BEEN TESTED WITH A 64-BIT GDB AND A 64-BIT
> TARGET. And it's a real HACK!!!
>
> But it does illustrate the problem.
>
> So, should I try to change GDB so that enable_thread_event() gets called after
> the dynamic loader has has a chance to relocate the .opd?
Here's my question: why isn't that happening already? Don't we get
shared library events after relocation processing? Or do we get one
before and one after?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-28 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 23:19 PAUL GILLIAM
2006-08-28 23:22 ` Daniel Jacobowitz [this message]
2006-08-28 23:31 ` PAUL GILLIAM
2006-08-29 19:04 ` Mark Kettenis
2006-08-29 19:08 ` Daniel Jacobowitz
2006-09-20 15:49 ` Daniel Jacobowitz
2006-09-20 17:41 ` John Reiser
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=20060828232206.GA27059@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=pgilliam@us.ibm.com \
--cc=sjmunroe@us.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