From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20496 invoked by alias); 31 Jan 2007 13:56:28 -0000 Received: (qmail 20487 invoked by uid 22791); 31 Jan 2007 13:56:26 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.suse.de (HELO mx1.suse.de) (195.135.220.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 31 Jan 2007 13:56:20 +0000 Received: from Relay1.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.suse.de (Postfix) with ESMTP id 48993122EC for ; Wed, 31 Jan 2007 14:56:17 +0100 (CET) From: Andreas Schwab To: gdb-patches@sourceware.org Subject: Re: Testsuite failures in gdb.base/callfuncs.exp References: <20070131124926.GA18380@nevyn.them.org> X-Yow: HELLO KITTY gang terrorizes town, family STICKERED to death! Date: Wed, 31 Jan 2007 13:56:00 -0000 In-Reply-To: <20070131124926.GA18380@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 31 Jan 2007 07:49:26 -0500") Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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: 2007-01/txt/msg00604.txt.bz2 Daniel Jacobowitz writes: > On Wed, Jan 31, 2007 at 01:33:26PM +0100, Andreas Schwab wrote: >> This fixes these testsuite failures on ia64: >> >> FAIL: gdb.base/callfuncs.exp: gdb function calls preserve register contents >> FAIL: gdb.base/callfuncs.exp: continue after stop in call dummy preserves register contents >> FAIL: gdb.base/callfuncs.exp: return after stop in call dummy preserves register contents >> >> The problem is that the bspstore register is specially tied with the bsp >> register, and this can't be controlled by gdb. > > How does this work - i.e. how do we guarantee that the restored state > is equivalent? Does it indicate extra registers written to the > register stack? bsp can only be modified by writing to bspstore, which is what the kernel does behind our back. gdb itself never writes to bspstore. Thus the value of bspstore does not really matter. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."