From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30286 invoked by alias); 22 Jan 2002 20:51:33 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 30234 invoked from network); 22 Jan 2002 20:51:29 -0000 Received: from unknown (HELO rj.sgi.com) (204.94.215.100) by sources.redhat.com with SMTP; 22 Jan 2002 20:51:29 -0000 Received: from rock.csd.sgi.com (fddi-rock.csd.sgi.com [130.62.69.10]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.1) with ESMTP id g0MKpSY09618; Tue, 22 Jan 2002 12:51:28 -0800 Received: from piet1.csd.sgi.com (piet1.csd.sgi.com [130.62.73.47]) by rock.csd.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id MAA32507; Tue, 22 Jan 2002 12:51:27 -0800 (PST) Received: (from piet@localhost) by piet1.csd.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) id MAA57868; Tue, 22 Jan 2002 12:51:27 -0800 (PST) Date: Tue, 22 Jan 2002 12:51:00 -0000 From: Piet/Pete Delaney To: Kevin Buettner Cc: gdb@sources.redhat.com, Piet Delaney Subject: Re: ia64-stub.c Message-ID: <20020122125127.A57796@sgi.com> References: <20020121010007.C54701@sgi.com> <1020121214310.ZM2318@localhost.localdomain> <20020122105652.A57552@sgi.com> <1020122190037.ZM5902@localhost.localdomain> <20020122121956.B57552@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020122121956.B57552@sgi.com> User-Agent: Mutt/1.3.23i X-SW-Source: 2002-01/txt/msg00248.txt.bz2 Terminal too wide I expected them to be offsets into the registers stored in memory in the order specified by the ia64_register_names[] array in gdb/ia64-tdep.c. I was also wondering if the macro REGISTER_RAW_SIZE in gdb/config/ia64/tm-ia64.h is correct. It's saying that all registers other that the floating point are 8 bytes long. I thought I read that the predict registers p0..p63 are 1 bit and packed into a single 64 bit chunk of memory. I was wondering if by passing all of the registers in the ia64_register_names I was passing to much and clobbering some data structures. When I use the gdb info registers cmd it seems to know the values in first 31 registers from my response to the 'g' cmd but then tries to access memory for the rest. The memory location it's trys to access is an offset from the values it receives for the first 31 registers. I thought I'd fix some linking problems that seem to have surfaced in my gdb-5.1 work space and place a loop in the code just prior to sending the 'g' packet. That way gdb will wait till I attach to the gdb instance that skdb forked off. -piet