From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29849 invoked by alias); 14 Jun 2003 09:54:47 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 29799 invoked from network); 14 Jun 2003 09:54:46 -0000 Received: from unknown (HELO fep06-app.kolumbus.fi) (193.229.0.57) by sources.redhat.com with SMTP; 14 Jun 2003 09:54:46 -0000 Received: from winxp ([62.248.130.255]) by fep06-app.kolumbus.fi with ESMTP id <20030614095445.EXVA22040.fep06-app.kolumbus.fi@winxp> for ; Sat, 14 Jun 2003 12:54:45 +0300 From: "Antti Havulinna" To: Subject: Debugging forked processes in Linux... Date: Sat, 14 Jun 2003 09:54:00 -0000 Message-ID: <005f01c3325a$f9ea6780$8a29770a@winxp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-SW-Source: 2003-06/txt/msg00274.txt.bz2 Any progress on the subject yet? Is there any (even unofficial) support in the Linux kernel for following the child-process after a fork? =A0 Best regards, =A0 Antti