From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jose Flavio Aguilar Paulino <jflavio@br.ibm.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 24700]
Date: Thu, 01 Mar 2007 21:56:00 -0000 [thread overview]
Message-ID: <1172786200.31150.11.camel@localhost.localdomain> (raw)
In-Reply-To: <20070301204046.GA5989@caradoc.them.org>
Hi,
I'm working with Flávio on this issue...
On Thu, 2007-03-01 at 15:40 -0500, Daniel Jacobowitz wrote:
> On Thu, Mar 01, 2007 at 05:05:36PM -0400, Jose Flavio Aguilar Paulino wrote:
> > The problem was that 'ppc64_linux_convert_from_func_ptr_addr()' first wanted to
> > make sure that the function pointer for 'malloc()' pointed into an .opd section
> > before it was 'dereferenced' It used 'target_section_by_addr()' to do the
> > search, and the section containing the PLT pointed to by the function pointer
> > was not in the section table being searched. But there is another section
> > table.
>
> Actually, there's a ton of section tables - this is an organizational
> problem in GDB. Originally they all meant different things.
>
> Does using find_pc_section instead work in all cases?
In the testcase mentioned here, GDB wants to allocate memory in the
inferior so that it can set the string's value. It's GDB that's calling
malloc and not the inferior, so the inferior's PC is not anywhere near
malloc (unless we're lucky), as far as I know...
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
next prev parent reply other threads:[~2007-03-01 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 18:27 Jose Flavio Aguilar Paulino
2007-03-01 18:37 ` Daniel Jacobowitz
2007-03-01 20:06 ` Jose Flavio Aguilar Paulino
2007-03-01 20:40 ` Daniel Jacobowitz
2007-03-01 21:56 ` Thiago Jung Bauermann [this message]
2007-03-01 22:03 ` Daniel Jacobowitz
2007-03-01 22:28 ` Thiago Jung Bauermann
2007-03-01 22:47 ` Andreas Schwab
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=1172786200.31150.11.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jflavio@br.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