linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Alex LIU <alex.liu@st.com>
Subject: Re: [uml-devel] Question about the unexpected signal 11 when fork in UML-2.6.7 TT mode
Date: Fri, 24 Jun 2005 12:17:56 +0200	[thread overview]
Message-ID: <200506241217.56423.blaisorblade@yahoo.it> (raw)
In-Reply-To: <000301c578a3$2cc33480$9eb3c68a@SHZ.ST.COM>

On Friday 24 June 2005 11:57, Alex LIU wrote:
> I just let the SIGSEVG go and return from the sleeping_process_signal
> function instead of tracer_panic and hanging the UML. It seems ok. Is it
> dangerous? Thanks a lot!
The sleeping process will get the SIGSEGV, with whatever content it has; 
hopefully it should handle it in kernel code but I'm not too sure about the 
situation. To ignore the signal you'll need a PTRACE_CONT (or PTRACE_SYSCALL, 
depending on the situation) with a 0 signal value.

However, is this related to the below problem? Did you try the other way 
around (i.e. upgrading) to solve it?
> Alex

> -----Original Message-----
> From: Blaisorblade [mailto:blaisorblade@yahoo.it]
> Sent: Tuesday, June 21, 2005 11:42 PM
> To: user-mode-linux-devel@lists.sourceforge.net
> Cc: Alex LIU
> Subject: Re: [uml-devel] Question about the unexpected signal 11 when fork
> in UML-2.6.7 TT mode
>
> On Tuesday 21 June 2005 12:05, Alex LIU wrote:
> > Hi,all:
> >
> > When I fork() in UML TT mode,it always said "the sleeping process xxx
> > received unexpedted signal 11" and the UML hang...before fork I also
> > set the signal handler... My UML is 2.6.7 and I used TT mode.Thanks a
> > lot!
> >
> > Alex
>
> Have you a good reason to use UML 2.6.7? We can't know by heart the list of
> all fixed bugs in previous UML releases, really, and you'll be doing
> yourself a favor by upgrading to 2.6.11-bs5 or 2.6.12 (which contains
> almost everything from -bs).
>
> That said, you are talking about userspace code, right? It's anyway strange
> that your system boots but you can't write a simple code that fork()'s.

-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2005-06-24 10:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 10:05 [uml-devel] Question about the unexpected signal 11 when fork in UML-2.6.7 TT mode Alex LIU
2005-06-21 15:41 ` Blaisorblade
2005-06-24  9:57   ` Alex LIU
2005-06-24 10:17     ` Blaisorblade [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=200506241217.56423.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=alex.liu@st.com \
    --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;
as well as URLs for NNTP newsgroup(s).