From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30287 invoked by alias); 22 Jun 2010 17:42:44 -0000 Received: (qmail 30275 invoked by uid 22791); 22 Jun 2010 17:42:44 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Jun 2010 17:42:40 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 35171130E3; Tue, 22 Jun 2010 10:42:37 -0700 (PDT) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id 2AA60C9A62; Tue, 22 Jun 2010 10:42:37 -0700 (PDT) Message-ID: <4C20F60C.5060409@vmware.com> Date: Tue, 22 Jun 2010 17:42:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.22 (X11/20090609) MIME-Version: 1.0 To: Edjunior Barbosa Machado CC: "gdb-patches@sourceware.org" Subject: Re: [PATCH] Quit after debugging corefiles References: <1277212708-11125-1-git-send-email-emachado@linux.vnet.ibm.com> In-Reply-To: <1277212708-11125-1-git-send-email-emachado@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-06/txt/msg00485.txt.bz2 Edjunior Barbosa Machado wrote: > Hello, > > when quitting after a successful debug using a corefile, gdb returns the following internal error: > > ... > (gdb) cont > Continuing. > > Program exited normally. > (gdb) quit Hmm, I don't think you're supposed to "continue" when debugging a core file... > ../../git/gdb/inferior.c:362: internal-error: find_inferior_pid: Assertion `pid != 0' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) n > ../../git/gdb/inferior.c:362: internal-error: find_inferior_pid: Assertion `pid != 0' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Create a core file of GDB? (y or n) n > > Please consider the following patch containing a fix and a new test for the gcore.exp testcase. It also proposes a change in the function called by gdb_test_multiple that deals with internal error (proc gdb_internal_error_resync{}, in gdb.exp) in order to recognize that gdb is finished. > > Comments/suggestions are welcome. > > Thanks,