This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: PDP-10
- To: Lars Brinkhoff <lars dot spam at nocrew dot org>
- Subject: Re: PDP-10
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Wed, 15 Nov 2000 01:02:59 +1100
- Cc: gdb at sourceware dot cygnus dot com
- References: <853djurgax.fsf@junk.nocrew.org> <39A641B6.25EDF1E1@cygnus.com> <8566oke1a7.fsf@junk.nocrew.org> <39CFA7E0.A7F93C52@cygnus.com> <85y9z59m7r.fsf@junk.nocrew.org>
Lars Brinkhoff wrote:
>
> Andrew Cagney <ac131313@cygnus.com> writes:
> > > I'm willing to give it a try. Would a PDP-10 target be acceptable
> > > for inclusion in GDB?
> > As a remote target? Yes. As native target, maybe :-)
>
> Well, I've signed a contract to write a native PDP-10 target. I just
> hope my work will be useful.
>
> > GDB needs to get its act together with respect to sizeof host/target
> > char. With respect to a native GDB, well, that could be more
> > interesting again. However, provided there is an active maintainer it
> > is still a possibility - depends mostly on the level of damage.
>
> Perhaps a bad idea, but how about something like defining bfd_byte
> to be a short on an 8-bit-char host debugging a greater-than-8-bit-char
> target? That way, the target memory could still be accessed as an
> array of chars, though with some memory overhead.
The problem isn't really with the target but rather with GDB
internally. It is doing computations to determine how big various data
structures are while at all times assuming that HOST_CHAR_BIT ==
TARGET_CHAR_BIT.
Fixing it may well involve first comming up with a clear guideline as to
where/when to use host/target char bit and then going through and fixing
all code so that it follows the guideline (and hence works correctly for
a PDP 10).
Andrew