This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Adding cross support for core files
- To: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Subject: Re: Adding cross support for core files
- From: Daniel Jacobowitz <drow at mvista dot com>
- Date: Thu, 1 Nov 2001 00:43:17 -0500
- Cc: binutils at sources dot redhat dot com, orjan dot friberg at axis dot com
- References: <200111010129.CAA14475@ignucius.axis.se>
On Thu, Nov 01, 2001 at 02:29:46AM +0100, Hans-Peter Nilsson wrote:
> I was going to just add a few macro and function definitions,
> using some generic linux core vector in bfd to enable inspection
> of cris-axis-linux-gnu core files (a WIP) for cross debugging.
>
> Then I noticed that it wasn't that easy. There's just no bfd
> support for cross corefile handling at all. Is there some good
> reason? I mean, other than that you have to do a bit of digging
> to get at the pt_regs and you have to specify struct user stuff
> cross-wise and such, and that there's a minor risk the layout
> might change (undetectably) between kernel releases.
>
> It looks like it wouldn't be too much work: a couple of
> well-placed #ifndef-#define-#endif:s in trad-core.c and a
> target-specific function or two for the binary digging. There's
> already support for a target-specific core header-file.
>
> Thoughts?
>
> brgds, H-P
> PS. It won't be ready this week.
Yes, it will :)
Why do you need trad-core.c? That is not for ELF cores. Does CRIS
dump in a.out?
For ELF cores, if you search the list archive, you'll see that I
implemented both BFD and GDB support for a large number of Linux cross
core targets. The framework's there; see the *_grok_* in elf32-mips.c
for an example implementation.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer