From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-8113-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 20995 invoked by alias); 22 Mar 2002 15:32:26 -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 20929 invoked from network); 22 Mar 2002 15:32:18 -0000
Received: from unknown (HELO mx.compgen.com) (158.155.2.6)
  by sources.redhat.com with SMTP; 22 Mar 2002 15:32:18 -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 g2MFW1u24307
	for <gdb@sources.redhat.com>; Fri, 22 Mar 2002 10:32:01 -0500
From: Jesse Marlin <jlm@compgen.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15515.20096.343244.71499@bass.compgen.com>
Date: Fri, 22 Mar 2002 07:32:00 -0000
To: gdb@sources.redhat.com
Subject: Can't attach to child using gdb-5.1.1 on Linux
X-Mailer: VM 6.89 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
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-03/txt/msg00194.txt.bz2


I have a process that forks a child.  If I try to attach to the
child it reads the symbols and shows an accurate stack trace, but when
I set a breakpoint and try to continue I get the following:

(gdb) c
Continuing.
lin-lwp.c:1003: gdb-internal-error: lin_lwp_wait: Assertion `WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed.
An internal GDB error was detected.  This may make further
debugging unreliable.  Continue this debugging session? (y or n) n

Create a core file containing the current state of GDB? (y or n) n

Inferior GDB exited abnormally with code 1


I answered yes to the above also, but it did not improve the situation.  Has
anybody seen this behvior before.  I am using gcc-2.95.3 for compilation.