From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30421 invoked by alias); 4 Apr 2002 14:26:44 -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 30367 invoked from network); 4 Apr 2002 14:26:39 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 4 Apr 2002 14:26:39 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 25C963E59; Thu, 4 Apr 2002 09:26:37 -0500 (EST) Message-ID: <3CAC629D.9000304@cygnus.com> Date: Thu, 04 Apr 2002 06:26:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.9) Gecko/20020328 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jlm@compgen.com Cc: gdb@sources.redhat.com Subject: Re: Can't attach to child using gdb-5.1.1 on Linux References: <15515.20096.343244.71499@bass.compgen.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00043.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. (not sure if someone has responded to this) The first thing to do is get a more recent GDB from: http://sources.redhat.com/gdb/current/ many problems have been fixed and if this problem still occures things have been narrowed down a bit. Andrew