This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Need Help for bringing m68k-based bdm target-patches formgdb-5.2.1 to gdb-5.3
- From: Andreas Schwab <schwab at suse dot de>
- To: Josef Wolf <jw at raven dot inka dot de>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 07 Aug 2003 08:08:11 +0200
- Subject: Re: Need Help for bringing m68k-based bdm target-patches formgdb-5.2.1 to gdb-5.3
- References: <20030731223514.GD20282@raven.inka.de><jed6fisl1z.fsf@sykes.suse.de> <20030806205431.GA3349@raven.inka.de>
Josef Wolf <jw@raven.inka.de> writes:
> Ough? Does that mean that gdb should not be used to debug supervisor mode?
GDB was designed to debug user level programs, which have no way to
see supervisor-only registers. So from GDB's point of view they don't
exist. That does not mean that GDB on m68k can not be extended to
handle them, you just need a way to get their contents from the target
(no current m68k target provides that).
>> Theses numbers are basically arbitrary, AFAIK.
>
> But there are places like
By arbitrary I mean not externally imposed. The numbers are chosen
for convenience inside GDB, and exposed only to the target interface,
where they are suitably translated when communicating with the target.
> BTW: I still don't have a clue what this MULTI_ARCH stuff is all about and
> how multi-arch targets are meant to be adopted.
MULTI_ARCH means that every target architecture hooks in through the
gdbarch structure at runtime, instead of hard coding the interface
characteristics at compile time. Targets that set GDB_MULTI_ARCH to
GDB_MULTI_ARCH_PARTIAL are not quite there yet, but the basic support
is present.
Andreas.