From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20045 invoked by alias); 24 Aug 2004 19:14:03 -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 20028 invoked from network); 24 Aug 2004 19:14:02 -0000 Received: from unknown (HELO us.ibm.com) (32.97.110.142) by sourceware.org with SMTP; 24 Aug 2004 19:14:02 -0000 Received: by us.ibm.com (Postfix, from userid 1000) id DEB7611B5C; Tue, 24 Aug 2004 12:11:53 -0700 (PDT) From: Paul Gilliam Reply-To: pgilliam@us.ibm.com To: gdb-patches@sources.redhat.com Subject: Re: Avoid timeouts in call-sc.exp Date: Tue, 24 Aug 2004 19:14:00 -0000 User-Agent: KMail/1.6.2 References: <200408181426.30208.pgilliam@us.ibm.com> <200408241148.06913.pgilliam@us.ibm.com> <412B8F25.nail1SD15JH17@mindspring.com> In-Reply-To: <412B8F25.nail1SD15JH17@mindspring.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408241211.53771.pgilliam@us.ibm.com> X-SW-Source: 2004-08/txt/msg00658.txt.bz2 On Tuesday 24 August 2004 11:55, Michael Chastain wrote: > Paul Gilliam wrote: > > 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? > > Two things at a time. > > The problem in call-sc.exp is that it assumes that the inferior > program is at a well-defined location after 'return'. When that's > not true, it derails. I want to get that fixed. > > The problem in gdb is that 'return' is the I/O error on fpscr. > > It's yet another issue about recognizing the outermost frame > on different ports, and I'm not going to care about that now. Fair enough. Fix call-sc.exp first, then look into the outer-most block thing as a seperate bug. -=# Paul #=-