From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: m68k, signals and single-stepping
Date: Thu, 30 Sep 2010 13:05:04 +0100 [thread overview]
Message-ID: <20100930120504.GM19804@ZenIV.linux.org.uk> (raw)
In-Reply-To: <m362xn63qc.fsf@hase.home>
On Thu, Sep 30, 2010 at 10:21:47AM +0200, Andreas Schwab wrote:
> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>
> >> So what's that SIGTRAP on exit from syscall in single-stepping mode for?
>
> The trace exception is low priority exception that is executed after all
> other exceptions are processed. So if the cpu single steps over a trap
> insns, the trace exception processing is started when the trap exception
> processing is complete, which is just before the cpu starts executing
> the trap exception handler in the kernel. You want the SIGTRAP to be
> sent to the user process, so you have to delay sending it until the
> kernel returns to user space.
Um... What's wrong with doing that from trap_c()?
next prev parent reply other threads:[~2010-09-30 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100930055823.GK19804@ZenIV.linux.org.uk>
2010-09-30 6:07 ` m68k, signals and single-stepping Geert Uytterhoeven
2010-09-30 8:21 ` Andreas Schwab
2010-09-30 12:05 ` Al Viro [this message]
2010-09-30 12:34 ` Andreas Schwab
2010-09-30 16:50 ` Al Viro
2010-10-02 3:44 ` Finn Thain
2010-10-02 11:23 ` Andreas Schwab
2010-10-02 11:57 ` Finn Thain
2010-10-02 12:27 ` Andreas Schwab
2010-09-30 8:25 ` Andreas Schwab
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=20100930120504.GM19804@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.