This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: What's with all the Cisco stuff?
- To: gatliff@haulpak.com
- Subject: Re: What's with all the Cisco stuff?
- From: Stan Shebs <shebs@cygnus.com>
- Date: Mon, 16 Aug 1999 19:00:01 -0700
- CC: jtc@redback.com, gdb@sourceware.cygnus.com
Date: Mon, 16 Aug 1999 15:57:45 -0500
From: William Gatliff <gatliff@haulpak.com>
> Stan> eCos and other folks observed that this was probably too
> Stan> heavyweight to impose on every RTOS, although it would make
> Stan> sense for the larger OSes.
>
> Even though I walked through the above thought experiment, I'm still
> not convinced that direct access to kernel data structures with GDB
> scripts is not superior.
I agree completely-- keeping a "thin" stub is definitely the way to go.
Absolutely, if it's possible.
In retrospect, what I'm after may be something less related to what you
guys are talking about than I thought... If I'm trying to make gdb
"aware" of an RTOS like uC/OS or eCos, for which I have sources, then the
kernel data structures should exist as symbols, so I should be able to
peek/poke at them with regular gdb functionality when the target stops.
Sources are convenient, although of course they're not available for
many OSes that we want to support. Also, you could run into a situation
where the OS sources changed slightly, so symbol-based scripts fail,
while a protocol-based design would continue to work.
Stan