From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25007 invoked by alias); 18 Jun 2008 23:12:56 -0000 Received: (qmail 24995 invoked by uid 22791); 18 Jun 2008 23:12:54 -0000 X-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,DATE_IN_FUTURE_24_48,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 18 Jun 2008 23:12:37 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m5INCRgh030107 for ; Wed, 18 Jun 2008 19:12:27 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5INCQLc010039; Wed, 18 Jun 2008 19:12:26 -0400 Received: from mopsy.redhat.com (vpn-10-22.bos.redhat.com [10.16.10.22]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5INCPdF020955; Wed, 18 Jun 2008 19:12:25 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18523.984.816283.299968@fleche.redhat.com> Date: Fri, 20 Jun 2008 13:45:00 -0000 To: Phil Muldoon Cc: frysk@sourceware.org Subject: Re: vfork thoughts In-Reply-To: <48565AD5.8050902@redhat.com> References: <48565AD5.8050902@redhat.com> X-Mailer: VM 8.0.9 under Emacs 22.2.1 (i386-redhat-linux-gnu) From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00110.txt.bz2 Phil> If anyone has a real life use case for debugging a vfork scenario we Phil> could model, that would help also. gcc uses vfork when spawning child processes. And, the code that actually does this does do some work between the vfork and the exec -- it is extremely common to move file descriptors around here. So, if you want to debug in this region, or just want to debug child processes created by vfork, gcc works :). There are probably a lot of other examples like this. Tom