From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19983 invoked by alias); 15 Feb 2012 14:00:45 -0000 Received: (qmail 19956 invoked by uid 22791); 15 Feb 2012 14:00:41 -0000 X-SWARE-Spam-Status: No, hits=-5.9 required=5.0 tests=AWL,BAYES_20,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Feb 2012 14:00:20 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q1FE0Gge018587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Feb 2012 09:00:17 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q1FE0Frg031763; Wed, 15 Feb 2012 09:00:16 -0500 Message-ID: <4F3BBA6F.4050209@redhat.com> Date: Wed, 15 Feb 2012 14:54:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120131 Thunderbird/10.0 MIME-Version: 1.0 To: Thomas Schwinge CC: gdb-patches@sourceware.org Subject: Re: [PATCH] [SH] Prologue skipping if there is none References: <87pqdgciho.fsf@schwinge.name> In-Reply-To: <87pqdgciho.fsf@schwinge.name> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: 2012-02/txt/msg00301.txt.bz2 Hey Thomas, On 02/15/2012 01:51 PM, Thomas Schwinge wrote: > First, for SH GNU/Linux, when running the testsuite via gdbserver on > pristine sources, I'm getting a large number of ERRORs, in the 350s. Is > that normal or at least known? They're basically all of the kind > ``ERROR: Process no longer exists'', and then follow-up errors until the > end of the specific testcase. From a very quick glance, they all seem to > be happening after the testcase has instructed GDB to invoke a function, > such as: > > (gdb) PASS: gdb.cp/classes.exp: print g_D.p > call class_param.Aptr_a (&g_A) > ERROR: Process no longer exists > UNRESOLVED: gdb.cp/classes.exp: call class_param.Aptr_a (&g_A) > ERROR: Couldn't send call class_param.Aptr_x (&g_A) to GDB. > > This probably suggests where to begin looking unless that's know already. This means that GDB crashed. Just run the test with $ ulimit -c unlimited $ make check RUNTESTFLAGS="classes.exp" so that the crash ends up creating a core, and you'll probably find that all the ERRORs are caused by a single bug. -- Pedro Alves