This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
RE: Building Insight for OpenRISC
- From: Keith Seitz <keiths at redhat dot com>
- To: Robert Cragie <rcc at jennic dot com>
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: 13 Aug 2003 10:15:28 -0700
- Subject: RE: Building Insight for OpenRISC
- Organization:
- References: <NMEDLDELHPEFHOMFIJBHAELBCNAA.rcc@jennic.com>
On Wed, 2003-08-13 at 10:00, Robert Cragie wrote:
> I see in bfd:
>
> coff-or32.c
> cpu-openrisc.c
> cpu-or32.c
> elf-openrisc.c
> elf-or32.c
>
> and in opcodes:
>
> openrisc-*.c
There appears to be BFD support, but no one appears to have ever
contributed a gdb port.
> It would be nice if both gdb and Insight were updated to include the
> OpenRISC CPU properly at some stage.
I suggest you get the people involved in the port to submit to the FSF.
It requires real work to do a debugger port for a processor and keep it
current with the fluctuating development. I'm sure there's a current
complier port because compilers are sexy and debuggers are not.
I suggest you hound the people who provide insight/gdb ports to formally
submit the port to mainline -- to give back a little something. Or you
could always attempt to do it yourself. :-)
Maybe someone has submitted? I don't know -- I don't track gdb that
closely anymore. You're much better off asking on the gdb list, where
hundreds of people hang out. As it is with insight, there is really just
me.
Wish I could be more helpful.
Keith