From owner-freebsd-hackers Wed Aug 19 08:18:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28466 for freebsd-hackers-outgoing; Wed, 19 Aug 1998 08:18:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28451 for ; Wed, 19 Aug 1998 08:18:47 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id KAA00649; Wed, 19 Aug 1998 10:18:07 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id KAA18099; Wed, 19 Aug 1998 10:17:35 -0500 Message-ID: <19980819101735.48927@right.PCS> Date: Wed, 19 Aug 1998 10:17:35 -0500 From: Jonathan Lemon To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: sfork()? References: <199808191303.PAA10187@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Alfred Perlstein on Aug 08, 1998 at 10:43:09AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 08, 1998 at 10:43:09AM -0500, Alfred Perlstein wrote: > > can someone explain why this doesn't work? Look at the -hacker archives, for a message from John Dyson titled "malloc() problems in children after using rfork()", circa Nov 1997. It includes an assembly wrapper around rfork() that is needed to make it work in userland. You apparently also need some assembly code to handle management of the stack; from my understanding, both processes will share the same stack on return from rfork(), and stomp on each other. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message