From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32584 invoked by alias); 24 Aug 2004 18:52:06 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 32572 invoked from network); 24 Aug 2004 18:52:05 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 24 Aug 2004 18:52:05 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1BzgOp-0004RP-Sx; Tue, 24 Aug 2004 14:52:03 -0400 Date: Tue, 24 Aug 2004 18:52:00 -0000 From: Daniel Jacobowitz To: Paul Gilliam Cc: gdb-patches@sources.redhat.com, Michael Chastain Subject: Re: Avoid timeouts in call-sc.exp Message-ID: <20040824185203.GA17045@nevyn.them.org> Mail-Followup-To: Paul Gilliam , gdb-patches@sources.redhat.com, Michael Chastain References: <200408181426.30208.pgilliam@us.ibm.com> <200408240913.38260.pgilliam@us.ibm.com> <412B7A5C.nailIQ211MRJW@mindspring.com> <200408241148.06913.pgilliam@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408241148.06913.pgilliam@us.ibm.com> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-08/txt/msg00653.txt.bz2 On Tue, Aug 24, 2004 at 11:48:06AM -0700, Paul Gilliam wrote: > Here is a diff between the two logs from where their difference is > non-trivial: > > < Running target unix/-m32 > --- > > Running target unix/-m64 > > 94,95c94,95 > < "finish" not meaningful in the outermost frame. > < (gdb) FAIL: gdb.base/call-sc.exp: finish foo; return call-sc-tc > --- > > Run till exit from #0 main () at ./gdb.base/call-sc.c:78 > > FAIL: gdb.base/call-sc.exp: finish foo; return call-sc-tc (timeout) > > Here is the $64000 question: why did GDB recognize we were in the > outermost frame for the 32-bit case and not for the 64-bit case? Is main() > not the outermost frame for ppc64 but is for ppc32? Guess I'll have to > break-down and check the API's. Probably GDB is confused about main and ".main"... -- Daniel Jacobowitz