From: Andreas Schwab <schwab@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Roland McGrath <roland@redhat.com>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: notify_parent (was: Re: Linux 2.6.9-rc2)
Date: Wed, 29 Sep 2004 14:14:07 +0200 [thread overview]
Message-ID: <jebrfpff1s.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.GSO.4.61.0409291403560.18029@waterleaf.sonytel.be> (Geert Uytterhoeven's message of "Wed, 29 Sep 2004 14:04:27 +0200 (MEST)")
Geert Uytterhoeven <geert@linux-m68k.org> writes:
>> > - /* We're back. Did the debugger cancel the sig? */
>> > - if (!(signr = current->exit_code)) {
>> > - discard_frame:
>> > - /* Make sure that a faulted bus cycle isn't
>> > - restarted (only needed on the 680[23]0). */
>> > - if (regs->format == 10 || regs->format == 11)
>> > - regs->stkadj = frame_extra_sizes[regs->format];
>>
>> This is important if you want continue after a SEGV.
>
> IC. But where should I do that?
Looks like we need a hook in the generic code.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-09-29 12:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.58.0409141420570.9444@waterleaf.sonytel.be>
2004-09-14 12:27 ` notify_parent (was: Re: Linux 2.6.9-rc2) Geert Uytterhoeven
2004-09-14 20:19 ` Roland McGrath
2004-09-15 9:02 ` Geert Uytterhoeven
2004-09-19 20:16 ` Geert Uytterhoeven
2004-09-19 22:31 ` Andreas Schwab
2004-09-29 12:04 ` Geert Uytterhoeven
2004-09-29 12:14 ` Andreas Schwab [this message]
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=jebrfpff1s.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=roland@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