From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15554 invoked by alias); 19 May 2005 15:58:59 -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 15342 invoked from network); 19 May 2005 15:58:52 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 19 May 2005 15:58:52 -0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DYnQC-0005js-4U; Thu, 19 May 2005 11:58:52 -0400 Date: Thu, 19 May 2005 15:58:00 -0000 From: Daniel Jacobowitz To: Wimmer Andreas Cc: gdb@sources.redhat.com Subject: Re: follow-fork-mode child on SuSE 9.2 (i586 and x86_64) not working Message-ID: <20050519155852.GA21994@nevyn.them.org> Mail-Followup-To: Wimmer Andreas , gdb@sources.redhat.com References: <1116510880.15960.11.camel@dibw112.joanneum.at> <20050519142215.GA18281@nevyn.them.org> <1116518244.14878.3.camel@dibw112.joanneum.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1116518244.14878.3.camel@dibw112.joanneum.at> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00193.txt.bz2 On Thu, May 19, 2005 at 05:57:24PM +0200, Wimmer Andreas wrote: > 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. I'm afraid that I haven't seen this problem, using kernels up to 2.6.11-rc3. Can you give me a simple testcase and a transcript of the session? -- Daniel Jacobowitz CodeSourcery, LLC