This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: Makefile setting
- To: Stephane dot Bihan at arccores dot com
- Subject: Re: Makefile setting
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Thu, 13 Apr 2000 19:02:45 +1000
- CC: gdb at sourceware dot cygnus dot com
- Organization: Cygnus Solutions
- References: <OFC6C77343.9E18E252-ON802568C0.002E5E4F@risccores.com>
Stephane.Bihan@arccores.com wrote:
>
> > > the ARC supported implementation of gdb we are trying to achieve is
> > > "extensible".
> > > The register description is minimal in the sense that only the basecase
> > > registers are described in REGISTER_NAMES.
> > > This description is updated (more registers are added) when we connect to
> the
> > > simulator.
> >
> > Hmm, I'd suggest investigating the multi-arch framework. It better
> > handles things like an architecture suddenly deciding it needs to be
> > changed. A target can also forced multi-arch to re-select its
> > architecture if needed.
> >
> > http://sourceware.cygnus.com/gdb/papers/multi-arch/
> >
> > For the register extensions, are they known by arcExtMap or are they
> > obtained from the target?
> >
> They are extracted from the object file.
Good, multi-arch should definitly help. When a new object file is
presented to GDB the multi-arch framework is asked to identify it and
create an architecture for it. arc-tdep.c can be set up to identify
that information and set up things like the REGISTER_NAME
(REGISTER_NAMES is being given the boot :-) for the relevant target.
Just a few speed bumps to climb over before it starts to help.
enjoy,
Andrew