From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [ppc64 help] Convert breakpoint's into addresses
Date: Mon, 22 Sep 2003 22:17:00 -0000 [thread overview]
Message-ID: <1030922221654.ZM29842@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "[ppc64 help] Convert breakpoint's into addresses" (Sep 19, 3:40pm)
On Sep 19, 3:40pm, Andrew Cagney wrote:
> I think the ppc64 ELF ABI is officially wierd.
>
> For "main" the minimal symbol table contains two symbols vis:
>
> main: points at descriptor in .opd sectoin
> .main: points at main's code entry point
>
> Consequently, given only a minimal symbol table, GDB, when given:
>
> (gdb) break main
>
> will try to insert the breakpoint in the descriptor, and not the
> function. Trying to enter:
>
> (gdb) break .main
>
> gets you no where (syntax error :-/)
>
> Adding to the fun, GCC's debug info contains the symbol "main" which
> points at the code address (and not the descriptor) and consequently
> debugging with symbols works. Yes, this means that "main" has two
> different values, arrrghghgh!!
Yuck. Is gcc simply broken or is there a good reason to do things this
way?
> Attatched is a hack to breakpoint.c that applies "convert from func ptr
> addr" to any address. This causing the breakpoint code to convert
> "main" into ".main" and hence work.
>
> I don't know if its a right fix, good fix, or of any other alternative
> fix. However it does work ...
> help!
>
> 2003-09-17 Andrew Cagney <cagney@redhat.com>
>
> * breakpoint.c (set_raw_breakpoint): Apply
> CONVERT_FROM_FUNC_PTR_ADDR to the breakpoint address.
> (breakpoint_re_set_one): Ditto.
I can't think of anything better. If this goes in, I suggest adding
a nice fat comment explaining what's going on...
Kevin
prev parent reply other threads:[~2003-09-22 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 19:41 Andrew Cagney
2003-09-22 22:17 ` Kevin Buettner [this message]
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=1030922221654.ZM29842@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.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