From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: m68k, signals and single-stepping
Date: Thu, 30 Sep 2010 10:21:47 +0200 [thread overview]
Message-ID: <m362xn63qc.fsf@hase.home> (raw)
In-Reply-To: <AANLkTimigeCBQdh1CxsxojKNGXWcoLQg10weE8w1r5v5@mail.gmail.com> (Geert Uytterhoeven's message of "Thu, 30 Sep 2010 08:07:05 +0200")
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.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-09-30 8:21 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 [this message]
2010-09-30 12:05 ` Al Viro
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=m362xn63qc.fsf@hase.home \
--to=schwab@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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