From: Daniel Jacobowitz <drow@false.org>
To: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: sigtramp shortcut
Date: Wed, 03 Mar 2004 00:37:00 -0000 [thread overview]
Message-ID: <20040303003748.GA29902@nevyn.them.org> (raw)
Message-ID: <20040303003700.saSpUCv5lVumGJrPxMxevb2GZjDu-nbX-ozTkXIwRrY@z> (raw)
[Sorry about breaking the thread - this came to me after deleting your
message...]
You could probably predicate the code inspection on find_pc_section. You're
looking for the kernel-generated trampoline if it has no name, so it should
be outside any of the objfiles GDB knows about - and this is one of a very
limited set of things (in most applications) that will meet that criteria.
Would that work?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2004-03-03 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Daniel Jacobowitz [this message]
2004-03-03 0:37 ` Daniel Jacobowitz
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=20040303003748.GA29902@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--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