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: Todd Whitesel <toddpw at windriver dot com>
- Subject: Re: gdb and the vxworks target
- From: jtc at redback dot com (J.T. Conklin)
- Date: 27 Oct 2000 10:25:18 -0700
- Cc: strauman at SLAC dot Stanford dot EDU (Till Straumann),gdb-patches at sources dot redhat dot com
- References: <200010270802.BAA14130@alabama.wrs.com>
- Reply-To: jtc at redback dot com
>>>>> "Todd" == Todd Whitesel <toddpw@windriver.com> writes:
>> 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.
Todd> Trying to bait me, eh? (Sorry, just took a few days to get
Todd> around to this.)
No, I wasn't trying to go that far. Just some good natured poking.
For what it's worth, the GDB remote protocol has the same "defect".
The register array is not specified, which makes it impossible for
someone to write either a debugger or a debug agent without looking
at the GDB sources to determine what goes where.
I actually like WDB quite a lot. You can see it was a significant
influence in my draft RDP II spec I sent out a few days ago.
--jtc
--
J.T. Conklin
RedBack Networks