From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-8412-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 5340 invoked by alias); 11 Apr 2002 21:43:59 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 5331 invoked from network); 11 Apr 2002 21:43:59 -0000
Received: from unknown (HELO mx.compgen.com) (158.155.2.6)
  by sources.redhat.com with SMTP; 11 Apr 2002 21:43:59 -0000
Received: from bass.compgen.com.compgen.com (IDENT:jlm@bass.compgen.com [158.155.4.59])
	by mx.compgen.com (8.11.6/8.11.6) with ESMTP id g3BLgNQ01744;
	Thu, 11 Apr 2002 17:42:24 -0400
From: Jesse Marlin <jlm@compgen.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15542.926.179306.808600@bass.compgen.com>
Date: Thu, 11 Apr 2002 14:43:00 -0000
To: Andrew Cagney <ac131313@cygnus.com>
Cc: jlm@compgen.com, gdb@sources.redhat.com
Subject: Re: Can't attach to child using gdb-5.1.1 on Linux
In-Reply-To: <3CB06E72.5080706@cygnus.com>
References: <15515.20096.343244.71499@bass.compgen.com>
	<3CAC629D.9000304@cygnus.com>
	<15532.31939.90386.425912@bass.compgen.com>
	<3CB06E72.5080706@cygnus.com>
Reply-To: jlm@compgen.com
X-Face: FbxF/xY<F@|f.|JNG)lOL.T0@>!V>vZ.$FXyN9:*'ZV?cib-\o'fWz2=}_Pb!#.JveZp_T18ZKC5T0RXNN=~_HPOF<X-]))4v@k"zVg(BQ$WN/TLSiy(5.UsehDm6*kK`j]\va%pe}7xUvl/4I@Ce6HVFP/P}Y/|74^~rO-CYcTf6+~VwiO;O0%
X-SW-Source: 2002-04/txt/msg00181.txt.bz2


Andrew Cagney writes:
 > > The stack traces look good before and after, but I can't debug anything.
 > > I did create a core file of gdb this time, and will submit if you want me
 > > to.
 > 
 > I don't know that the core fill will be of much use. However, a test 
 > case and the backtrace from the GDB core file would be.

In the general case this seems to work (ie. fork and try to attach to a
sleeping child).  My program seems to be doing something that causes gdb
to behave differently.  I am still trying to generate a test case for it.