From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fixes problem setting breakpoint in dynamic loader
Date: Thu, 14 Jun 2007 23:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0706142332100.23187@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1177701733.10993.27.camel@localhost.localdomain>
On Fri, 27 Apr 2007, Thiago Jung Bauermann wrote:
> Hi folks,
>
> This is a re-submission of:
>
> http://sourceware.org/ml/gdb-patches/2006-07/msg00264.html
This doesn't work properly for me. There seem to be at least two problems
with relying on the implicit conversion by
ppc_linux_convert_from_func_ptr_addr done when setting a breakpoint:
* ppc_linux_convert_from_func_ptr_addr relies on being able to find the
function descriptor address in a section table, but doesn't have current
information about the load address of ld.so which has only just been
determined in enable_break.
* The function descriptor in ld.so has not yet been relocated (as part of
ld.so applying relocations to itself) at the time this breakpoint is set.
So after the address is extracted from the function descriptor, the load
address of ld.so must be added to it again. (I think this provides an
answer to Andreas's question in
<http://sourceware.org/ml/gdb-patches/2006-07/msg00183.html>: the explicit
conversion is needed so that this relocation applies when load_addr gets
added to the address later before the breakpoint is set.)
I have a patch version partly based on the earlier revision
<http://sourceware.org/ml/gdb-patches/2006-07/msg00019.html> which does
set the breakpoint correctly, but I still have other GDB problems I'm
investigating with that patch applied.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2007-06-14 23:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 20:59 Thiago Jung Bauermann
2007-06-14 23:38 ` Joseph S. Myers [this message]
2007-06-20 13:15 ` Daniel Jacobowitz
2007-06-20 14:21 ` Daniel Jacobowitz
2007-06-22 14:07 ` Thiago Jung Bauermann
2007-06-20 14:39 ` Ulrich Weigand
2007-06-25 21:28 ` Ulrich Weigand
2007-07-03 15:58 ` Daniel Jacobowitz
2007-06-26 18:43 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2006-05-25 2:26 [patch] " PAUL GILLIAM
2006-05-25 16:27 ` Daniel Jacobowitz
2006-05-25 22:58 ` PAUL GILLIAM
2006-05-25 23:12 ` Daniel Jacobowitz
2006-05-27 17:52 ` PAUL GILLIAM
2006-06-23 21:33 ` PAUL GILLIAM
2006-06-23 21:48 ` Mark Kettenis
2006-06-26 22:21 ` PAUL GILLIAM
2006-06-26 22:28 ` PAUL GILLIAM
2006-06-26 23:55 ` Kevin Buettner
2006-06-26 18:48 ` Kevin Buettner
2006-06-17 20:21 ` Mark Kettenis
2006-07-06 1:01 ` PAUL GILLIAM
2006-07-06 2:57 ` Daniel Jacobowitz
2006-07-06 16:10 ` Kevin Buettner
2006-07-16 18:57 ` Andreas Schwab
2006-07-19 21:55 ` PAUL GILLIAM
2006-05-20 6:21 [PATCH] -var-update Nick Roberts
2006-05-20 16:34 ` Daniel Jacobowitz
2006-05-21 2:04 ` Nick Roberts
2006-05-21 5:22 ` Daniel Jacobowitz
2006-05-21 23:04 ` Nick Roberts
2006-05-25 0:21 ` Nick Roberts
2006-05-25 0:26 ` [patch] Fixes problem setting breakpoint in dynamic loader PAUL GILLIAM
2006-05-25 0:29 ` PAUL GILLIAM
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=Pine.LNX.4.64.0706142332100.23187@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bauerman@br.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