From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12698 invoked by alias); 19 May 2005 15:57:54 -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 12274 invoked from network); 19 May 2005 15:57:33 -0000 Received: from unknown (HELO rzjgate.joanneum.ac.at) (143.224.185.1) by sourceware.org with SMTP; 19 May 2005 15:57:33 -0000 Received: from RZJC2EX.jr1.local (rzjs028.joanneum.ac.at [143.224.71.152]) by rzjgate.joanneum.ac.at (8.13.1/8.13.1) with ESMTP id j4JFvxCu000216; Thu, 19 May 2005 17:57:59 +0200 (MEST) Received: from 143.224.67.90 ([143.224.67.90]) by RZJC2EX.jr1.local ([143.224.71.154]) with Microsoft Exchange Server HTTP-DAV ; Thu, 19 May 2005 15:57:25 +0000 Received: from dibw112 by rzjc2ex.joanneum.at; 19 May 2005 17:57:24 +0200 Subject: Re: follow-fork-mode child on SuSE 9.2 (i586 and x86_64) not working From: Wimmer Andreas Reply-To: andreas.wimmer@joanneum.at To: Daniel Jacobowitz Cc: gdb@sources.redhat.com In-Reply-To: <20050519142215.GA18281@nevyn.them.org> References: <1116510880.15960.11.camel@dibw112.joanneum.at> <20050519142215.GA18281@nevyn.them.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 19 May 2005 15:57:00 -0000 Message-Id: <1116518244.14878.3.camel@dibw112.joanneum.at> Mime-Version: 1.0 X-SW-Source: 2005-05/txt/msg00192.txt.bz2 On Thu, 2005-05-19 at 10:22 -0400, Daniel Jacobowitz wrote: > On Thu, May 19, 2005 at 03:54:40PM +0200, Wimmer Andreas wrote: > > Hi, > > I am using SuSE 9.2 both on i586 and x86_64 platforms and have some > > troubles to get the follow-fork-mode=child feature working > > The system is using the kernels provided by the distribution > > 2.6.8-11.24 (based on 2.6.8 ?) > > I tried with the distribution provided gdb (6.2.1) and also with 6.3 > > all with the same effect. > > *) A debugged program starts up normally untill it reaches a fork > > statement > > *) The child process is created the debugger detects the child and > > gives the message "Attaching after fork to child process .." > > *) The child runs a while (it executed some of the initial code after > > the fork) and then blocks > > *) After that GDB also blocks without any chance to do something > > > > NOTE: the parent process is left in "S+" state and the child remains in > > "T+" state. > > Can you reproduce this without using a SuSE kernel? If not, you may > want to report this to SuSE. Yes I can reproduce this on a a vanilla 2.6.11.10 kernel which I just compiled for testing. Same situation, gdb and child process are blocked, without any further debugging possible. --------------------- Andreas Wimmer Joanneum Research