From: Jeff Dike <jdike@addtoit.com>
To: "Stroesser, Bodo" <Bodo.Stroesser@fujitsu-siemens.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
BlaisorBlade <blaisorblade_spam@yahoo.it>
Subject: Re: [uml-devel] Signal handling: deliver segfault immediately
Date: Thu, 30 Sep 2004 21:39:56 -0400 [thread overview]
Message-ID: <200410010139.i911duqR004609@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 30 Sep 2004 17:29:06 +0200." <8B6FF516CBA0194AB0996705076B02520F7C3F@ABGEX01E.abg.fsc.net>
> - if(sig > 0){
> + while ( (sig = get_signal_to_deliver(&info, &ka_copy, regs,
> NULL)) ) {
This one makes me nervous. I never checked that nesting signal frames for
multiple pending signals works, although the frame format is identical, so
it should.
Have you checked that?
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-01 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 15:29 [uml-devel] Signal handling: deliver segfault immediately Stroesser, Bodo
2004-10-01 1:39 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-01 8:10 Stroesser, Bodo
2004-10-05 5:26 ` Jeff Dike
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=200410010139.i911duqR004609@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=Bodo.Stroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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