Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [ppc64-linux]: skip linkage functions
Date: Fri, 06 Jun 2003 22:47:00 -0000	[thread overview]
Message-ID: <vt2isrix1q4.fsf@zenia.home> (raw)
In-Reply-To: <20030606214003.GA11393@nevyn.them.org>


Daniel Jacobowitz <drow@mvista.com> writes:
> On Fri, Jun 06, 2003 at 03:31:58PM -0500, Jim Blandy wrote:
> > Daniel Jacobowitz <drow@mvista.com> writes:
> > > What blows up if we don't recognize the trampolines though?
> > 
> > On the PPC64, 'next' blows up.
> 
> Oh, I hit this problem on another platform recently.  And I had to do a
> similar hack for trampolines.
> 
> It seems that there shold be a simpler solution than trying to parse
> the trampoline...

Well, the only relevant piece of machine state is the PC.  From there
you can either look at the code (trampoline parsing), or look at
meta-information associated with the address (DW_AT_trampoline).  That
exhausts the possibilities, doesn't it?

A simpler meta-information approach might be to insert some new sort
of symbol (STT_GNU_TRAMPOLINE?) whose value was the start address of
the trampoline, and whose name was the name of the function the
trampoline called.  Then in_solib_call_trampoline would just check for
an STT_GNU_TRAMPOLINE symbol, and skip_trampoline_code would return
the value of the STT_FUNC symbol of the same name.


  reply	other threads:[~2003-06-06 22:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 23:54 Jim Blandy
2003-06-06  0:03 ` Daniel Jacobowitz
2003-06-06  6:22   ` Jim Blandy
2003-06-06 13:11     ` Daniel Jacobowitz
2003-06-06 20:09       ` Jim Blandy
2003-06-06 20:17         ` Daniel Jacobowitz
2003-06-06 20:31           ` Jim Blandy
2003-06-06 21:40             ` Daniel Jacobowitz
2003-06-06 22:47               ` Jim Blandy [this message]
2003-06-10  0:05 ` Kevin Buettner
2003-06-10 17:29   ` Jim Blandy

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=vt2isrix1q4.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=drow@mvista.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