From: Aleksandar Ristovski <aristovski@qnx.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Stepping out of signal handler problem
Date: Fri, 16 May 2008 18:48:00 -0000 [thread overview]
Message-ID: <482DD704.70808@qnx.com> (raw)
In-Reply-To: <200805161732.m4GHWcjU013412@brahms.sibelius.xs4all.nl>
Mark Kettenis wrote:
>> From: Aleksandar Ristovski <aristovski@qnx.com>
>> Date: Fri, 16 May 2008 12:26:43 -0400
>>
>> This makes question 2: Is the only way to implement this similar to
>> linux-nat (scanning for sigreturn kernel call)? Is there anything
>> 'cleaner'?
>
> The clean way of doing this is provide proper unwind info for the
> signal trampoline. This shouldn't be too difficult if your signal
> trampolines live in libc, and quite a bit harder if they are in the
> kernel.
>
What is the preferred way: frame_unwind_append_sniffer or tramp_frame_prepend_unwinder?
next prev parent reply other threads:[~2008-05-16 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 16:27 Aleksandar Ristovski
2008-05-16 17:33 ` Mark Kettenis
2008-05-16 18:48 ` Aleksandar Ristovski [this message]
2008-05-16 20:42 ` Mark Kettenis
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=482DD704.70808@qnx.com \
--to=aristovski@qnx.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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