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: gdb@sourceware.cygnus.com
- Subject: Re: What's with all the Cisco stuff?
- From: Tom Tromey <tromey@cygnus.com>
- Date: 13 Aug 1999 00:01:31 -0600
- DJ-Gateway: from newsgroup cygnus.gdb
- Newsgroups: cygnus.gdb
- Organization: Cygnus Solutions
- References: <199908122301.QAA03422@andros.cygnus.com>
- Reply-To: tromey@cygnus.com
>>>>> "Stan" == Stan Shebs <shebs@cygnus.com> writes:
Stan> Alternatively, modules could be made dynamically loadable, and I
Stan> think that is the right long-term direction; everything still
Stan> works the same from the user point of view, and simplifies the
Stan> base debugger. Indeed, Fernando tangled with this for kod, the
Stan> results indicating that getting dynamic loading right everywhere
Stan> is a nontrivial task.
FWIW, getting this right for most useful host systems is easy: use
`libltdl', which comes with libtool. I decided not to do this for
kod-cisco.c because I lost interest and time. If someone wants to
libtoolize kod-cisco.c and add the required code to kod.c (and ltdl to
the build infrastructure) I would be happy to provide pointers and
advice.
It would be nice if different parts of gdb could be dynamically
loaded. For instance, I'd rather not have support for Modula-2, or
Scheme, or even Java (shock, horror) unless I was debugging an
executable that needed these bits. (This presumes that the savings
are worth the effort. I haven't looked to see whether this is so, and
I suspect they are not.)
Tom