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


On 01 Apr 2009, at 21:14, Daniel Jacobowitz wrote:

> On Wed, Apr 01, 2009 at 09:08:11PM +0200, Jonas Maebe wrote:
>>>
> GDB already supports this for other languages; I suggest just adding
> detection of the Free Pascal stubs to the debugger.  ObjC and C++
> both have similar requirements, I believe.  In C++ they're virtual
> call thunks.

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?


Jonas


  reply	other threads:[~2009-04-01 20:15 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 [this message]
2009-04-01 20:20     ` Daniel Jacobowitz
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=83CD35E6-FDD6-4A4B-A5E2-14AC30D609DA@elis.ugent.be \
    --to=jonas.maebe@elis.ugent.be \
    --cc=gdb@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