This is the mail archive of the
mailing list for the GDB project.
- From: Piet/Pete Delaney <piet at sgi dot com>
- To: Kevin Buettner <kevinb at redhat dot com>
- Cc: gdb at sources dot redhat dot com, Piet Delaney <piet at sgi dot com>
- Date: Tue, 22 Jan 2002 12:51:27 -0800
- Subject: Re: ia64-stub.c
- References: <20020121010007.C54701@sgi.com> <1020121214310.ZM2318@localhost.localdomain> <20020122105652.A57552@sgi.com> <1020122190037.ZM5902@localhost.localdomain> <20020122121956.B57552@sgi.com>
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.