This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH]: some gdbserver changes for NetBSD/powerpc
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: [PATCH]: some gdbserver changes for NetBSD/powerpc
- From: jtc at redback dot com (J.T. Conklin)
- Date: 21 Nov 2000 10:39:53 -0800
- Cc: gdb-patches at sourceware dot cygnus dot com
- References: <5mzoiutbe9.fsf@jtc.redback.com> <3A19C595.C68BB144@cygnus.com>
- Reply-To: jtc at redback dot com
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
>> Does anyone have an example of a multi-arched gdbserver? For gnu/linux
>> ppc perhaps?
Andrew> I don't know that trying to multi-arch gdbserver is useful.
Andrew> The gdb server is normally built to run on a specific host so
Andrew> supporting other hosts is kind of wierd. The only situtation
Andrew> where I can see it being useful is for a platform that
Andrew> provides multiple kernel interfaces (NetBSD has Linux compat
Andrew> mode; Solaris SPARC 32/64) and there I'm not sure of the
Andrew> tradeoffs. Simply building two gdbserver binaries would be
Andrew> easier.
I'm not really trying to build a gdbserver that can handle multiple
architectures/targets, but rather fix the netbsd/ppc gdbserver that
got broken when the gdb ppc target was multi-arched. In this case,
REGISTER_BYTES and MAX_REGISTER_RAW_SIZE which used to be defined as
constants, are now gdbarch functions. This causes compile time
failures since these macros are used to size arrays.
I'm looking for direction for fixing this.
--jtc
--
J.T. Conklin
RedBack Networks