On Wed, 2002-11-06 at 13:12, Andrew Cagney wrote:
> Instead of having to add this to the standard gdb as a one-off for NGPT,
> I can use the standard gdb and design them as plug-ins to be loaded only
> when debugging NGPT applications. This feels a lot cleaner and could be
> applied for other gdb features/architectures to keep the core as small
> and efficient as possible, loading additional support/features on demand
> only when needed.
That is the theory already. Reality differs though, there is always
more work to do :-(. That work is, however, independant of a plug-in
module.
Andrew,
Can you clarify what you mean here? You seem to be implying that there
are plans to support on demand (dynamic) loading of features, which
sounds a lot like plug-ins.
GDB's current architecture allows the relatively easy addition of new
components (a new language, a new remote backend, a new isa) - add the
file to the source list and re-compile. In theory, you don't need to go
around modifying lots of headers and the like.