From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14503 invoked by alias); 24 Aug 2004 17:26:37 -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 14491 invoked from network); 24 Aug 2004 17:26:36 -0000 Received: from unknown (HELO barry.mail.mindspring.net) (207.69.200.25) by sourceware.org with SMTP; 24 Aug 2004 17:26:36 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by barry.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1Bzf48-0005dK-00; Tue, 24 Aug 2004 13:26:36 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id B6F604B102; Tue, 24 Aug 2004 13:26:53 -0400 (EDT) Date: Tue, 24 Aug 2004 17:26:00 -0000 From: Michael Chastain To: pgilliam@us.ibm.com Subject: Re: Avoid timeouts in call-sc.exp Cc: gdb-patches@sources.redhat.com Message-ID: <412B7A5C.nailIQ211MRJW@mindspring.com> References: <200408181426.30208.pgilliam@us.ibm.com> <200408231408.53088.pgilliam@us.ibm.com> <412A67E6.nailD782KDIOT@mindspring.com> <200408240913.38260.pgilliam@us.ibm.com> In-Reply-To: <200408240913.38260.pgilliam@us.ibm.com> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00649.txt.bz2 Good logs! Both of the logs show similar de-synchronization. The problem starts here in ppc32.gdb.log: p/c L $2 = 90 'Z' (gdb) PASS: gdb.base/call-sc.exp: zed L for return; return call-sc-tc return foo Make fun return now? (y or n) y reading register fpscr (#70): Input/output error. (gdb) FAIL: gdb.base/call-sc.exp: return foo; return call-sc-tc p/c L $3 = 90 'Z' (gdb) FAIL: gdb.base/call-sc.exp: value foo returned; return call-sc-tc advance fun main () at ./gdb.base/call-sc.c:78 78 L = fun (); (gdb) FAIL: gdb.base/call-sc.exp: advance to fun for finish; return call-sc-tc p/c L I presume the I/O error on fpscr is a bug in gdb. After the bug happens, variable 'L' is not set to its new value. And then "advance" starts from some de-synchronized place. ppc64.gdb.log has the same problem.