This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: gdb and the vxworks target
- To: jtc at redback dot com
- Subject: Re: gdb and the vxworks target
- From: Todd Whitesel <toddpw at windriver dot com>
- Date: Fri, 27 Oct 2000 01:02:50 -0700 (PDT)
- Cc: strauman at SLAC dot Stanford dot EDU (Till Straumann), gdb-patches at sources dot redhat dot com
> It's OK, but at least in the copy of the WDB spec I have there are
> some holes, such as in what set and at what offset each register is
> located for the get/fetch register commands. I wasn't able to find
> the WTX or WDB specs in the Tornado II documentation --- I got the
> impression that they (WRS) wants to hide such details under their
> proprietary libraries. That makes it a bit difficult for third party,
> open source, multi-platform tools like GDB.
Trying to bait me, eh? (Sorry, just took a few days to get around to this.)
The protocol libraries DON'T KNOW anything about registers; they just provide
read/write access to the TCB register area and trust the application layer
to know what register it is going to be tweaking.
Every Tornado customer gets both the header files containing the TCB layout
(target/h/arch/*/regs*.h) as well as the Tcl code GDB uses to find them
(host/resource/tcl/gdb.tcl), so any hiding that's going on is from EVERYONE
including WRS employees and contractors who have to constantly keep these
files up-to-date.
I would have preferred a target query to enumerate the register set.
--
Todd Whitesel
toddpw @ windriver.com