Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Jonas Maebe <jonas.maebe@elis.ugent.be>
Cc: gdb@sourceware.org
Subject: Re: Skipping over trampolines/stubs
Date: Wed, 01 Apr 2009 20:20:00 -0000	[thread overview]
Message-ID: <20090401201952.GA22834@caradoc.them.org> (raw)
In-Reply-To: <83CD35E6-FDD6-4A4B-A5E2-14AC30D609DA@elis.ugent.be>

On Wed, Apr 01, 2009 at 10:15:33PM +0200, Jonas Maebe wrote:
> Thanks. Given that tracing some of these stubs requires access to the  
> parameters, I should start with adding support for the Borland fastcall 
> calling convention to gdb. The reason is that this is our default calling 
> convention on i386 platforms, mainly for Delphi compatibility reasons 
> (quite a bit of unparametrised assembler code there).
>
> Which brings me to the next point: how does one go about "allocating" a 
> new DW_AT_calling_convention value in the DW_CC_lo_user .. DW_CC_hi_user 
> range? At first sight, there is only one such value currently in public 
> use (DW_CC_GNU_renesas_sh). Can I just take 0x41 for 
> DW_CC_BORLAND_fastcall_i386? And should I then submit this constant for 
> inclusion in binutils first?

I don't know - might want to raise this on the DWARF discussion list
(see dwarfstd.org).

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-04-01 20:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 19:08 Jonas Maebe
2009-04-01 19:14 ` Daniel Jacobowitz
2009-04-01 20:15   ` Jonas Maebe
2009-04-01 20:20     ` Daniel Jacobowitz [this message]
2009-04-01 21:40       ` Jonas Maebe

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=20090401201952.GA22834@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=jonas.maebe@elis.ugent.be \
    /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