linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-user@lists.sourceforge.net, schauer@acousta.at
Cc: Rob Landley <rob@landley.net>,
	user-mode-linux-devel@lists.sourceforge.net,
	Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: Problems about fork-not-clone (was: Re: [uml-user] UML exits after "tracing thread pid")
Date: Tue, 12 Jul 2005 17:57:55 +0200	[thread overview]
Message-ID: <200507121757.55572.blaisorblade@yahoo.it> (raw)
In-Reply-To: <1121160835.4718.3.camel@FC3-bernhard-1.acousta.local>

On Tuesday 12 July 2005 11:33, Bernhard Schauer wrote:
> > Checking PROT_EXEC mmap in /tmp...OK
> > tracing thread pid = 11687
> >
> > And then exits with no further explanation or printout.
>
> That sounds like the behaviour described in the first message. If you
> apply the
> "uml-revert-fork-instead-of-clone.patch" posted by Blaisorblade in the
> same thread on 2nd July, everything should work as expected with TT mode
> only.
Exact, that's included in -bs which is included in the -skas0 patchset, so 
this is the explaination.
-- 
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



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
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-12 15:50 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       ` [uml-devel] " 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 [this message]
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=200507121757.55572.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=rob@landley.net \
    --cc=schauer@acousta.at \
    --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