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 19:14:00 -0000 [thread overview]
Message-ID: <20090401191446.GA18926@caradoc.them.org> (raw)
In-Reply-To: <4B835C7C-B28E-4552-87E0-25D803741FA3@elis.ugent.be>
On Wed, Apr 01, 2009 at 09:08:11PM +0200, Jonas Maebe wrote:
> So I'm wondering whether there's maybe some trick that you can use to
> make gdb step through arbitrary stubs somehow (maybe some kind of fake
> line information that it always ignores and just skips over), or whether
> there is another possible approach.
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-04-01 19:14 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 [this message]
2009-04-01 20:15 ` Jonas Maebe
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=20090401191446.GA18926@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