From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Problems about fork-not-clone (was: Re: [uml-user] UML exits after "tracing thread pid")
Date: Thu, 7 Jul 2005 07:59:08 -0400 [thread overview]
Message-ID: <20050707115908.GA6043@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200507041853.13469.blaisorblade@yahoo.it>
> Ok, can you describe it a bit more detailedly?
>
> Also, are you going to drop this patch (or allow me to do this) for now?
> Since it isn't getting fixed, it seems me a good idea.
I still think the patch is correct. Ben LaHaise sent me a UML binary
which crashes, which I can send you if you want to look at it.
This thing was looking at errno after the first call to fork even if
it succeeded. This leads me to believe that this is a compiler oddity
rather than a compiler bug, and that this is causing UML to hit the
tt-specific errno crash with recent libcs. You understand that
problem more than I do.
So, I would say that skas0 is more a fix for this problem than
reverting the fork-not-clone patch is.
Jeff
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-07-07 11:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1119527920.4679.15.camel@FC3-bernhard-1.acousta.local>
[not found] ` <1119614544.4643.9.camel@FC3-bernhard-1.acousta.local>
[not found] ` <20050624134118.GA4117@ccure.user-mode-linux.org>
2005-07-04 16:53 ` [uml-devel] Problems about fork-not-clone (was: Re: [uml-user] UML exits after "tracing thread pid") Blaisorblade
2005-07-07 11:59 ` Jeff Dike [this message]
2005-07-07 18:31 ` [uml-devel] " Blaisorblade
2005-07-11 7:48 ` Bernhard Schauer
2005-07-11 21:21 ` Blaisorblade
2005-07-12 7:53 ` Rob Landley
2005-07-12 8:04 ` Rob Landley
2005-07-12 9:33 ` Bernhard Schauer
2005-07-12 15:57 ` Blaisorblade
2005-07-12 18:54 ` Rob Landley
2005-07-13 13:36 ` Blaisorblade
2005-07-12 7:55 ` [uml-devel] Re: Problems about fork-not-clone Bernhard Schauer
2005-07-12 16:16 ` [uml-user] " Blaisorblade
2005-07-15 3:05 ` Michael Richardson
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=20050707115908.GA6043@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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 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.