This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: cross targeted gdb and corefiles
- From: "Kevin \"Squail\" Endres" <kevine at wildseed dot com>
- To: 'Kevin Buettner' <kevinb at redhat dot com>, "Kevin \"Squail\" Endres" <kevine at wildseed dot com>, 'Daniel Jacobowitz' <drow at mvista dot com>, Richard dot Earnshaw at arm dot com
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 16 May 2002 15:43:18 -0700
- Subject: RE: cross targeted gdb and corefiles
ahh - so i need to find out what gregset_t and fpregset_t should be.... any
hits where to look??
:]k
-----Original Message-----
From: Kevin Buettner [mailto:kevinb@redhat.com]
Sent: Thursday, May 16, 2002 3:33 PM
To: Kevin "Squail" Endres; 'Kevin Buettner'; 'Daniel Jacobowitz';
Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: cross targeted gdb and corefiles
On May 16, 3:27pm, Kevin \Squail\ Endres wrote:
> Yep had just figured out to move the supply_* (and the nwfpe*) functions
> from arm-linux-nat.c to arm-linux-tdep.c. I did assume that the kernel
> headers needed to be from an arm configured kernel so i set the prefix to
> the root of my cross toolchain whemn i configured.
>
> everything builds but when i try to read an arm core i get a warning about
> the size of the gregset struct in the core (so possibly i am truly not
> including the correct headers??)
The trick is to not depend on the headers at all.
One way to do this is to define (in the tdep.c file) the necessary
structs entirely in terms of chars. (This includes adding in any ABI
mandated padding between fields.)
Kevin