From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13828 invoked by alias); 22 Jun 2010 13:22:39 -0000 Received: (qmail 13817 invoked by uid 22791); 22 Jun 2010 13:22:39 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 Jun 2010 13:22:35 +0000 Received: (qmail 15765 invoked from network); 22 Jun 2010 13:22:33 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 22 Jun 2010 13:22:33 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [PATCH] Quit after debugging corefiles Date: Tue, 22 Jun 2010 13:22:00 -0000 User-Agent: KMail/1.13.2 (Linux/2.6.32-22-generic; KDE/4.4.2; x86_64; ; ) Cc: Edjunior Barbosa Machado 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> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201006221422.29390.pedro@codesourcery.com> 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/msg00479.txt.bz2 On Tuesday 22 June 2010 14:18:28, Edjunior Barbosa Machado wrote: > Hello, > > when quitting after a successful debug using a corefile, gdb returns the following internal error: > > ... > (gdb) cont > Continuing. Please refer to last month's "Forbid run with a core file loaded" thread. > > Program exited normally. > (gdb) quit > ../../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, > -- Pedro Alves