linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-user@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Problems about fork-not-clone (was: Re: [uml-user] UML exits after "tracing thread pid")
Date: Mon, 4 Jul 2005 18:53:12 +0200	[thread overview]
Message-ID: <200507041853.13469.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050624134118.GA4117@ccure.user-mode-linux.org>

On Friday 24 June 2005 15:41, Jeff Dike wrote:
> On Fri, Jun 24, 2005 at 02:02:24PM +0200, Bernhard Schauer wrote:
> > Checking for host processor xmm support...No
> > Checking that ptrace can change system call numbers...<0>Kernel panic -
> > not syncing: Segfault with no mm
>
> Revert the fork-not-clone patch:
> 	http://www.ussg.iu.edu/hypermail/linux/kernel/0506.1/0665.html
>
> The patch isn't wrong exactly - as far as I can see, the compiler is
> compiling it slightly differently so that it hits the tt mode vs new libc
> errno incompatibility.
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.
-- 
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-07-04 16:47 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     ` Blaisorblade [this message]
2005-07-07 11:59       ` [uml-devel] Re: Problems about fork-not-clone (was: Re: [uml-user] UML exits after "tracing thread pid") Jeff Dike
2005-07-07 18:31         ` 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=200507041853.13469.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox