Idea for improving the GDB plugin

[rickg22]

This idea came to me as I was debugging the debugger (lol ) plugin. There's usually the construct

Code Select Expand


cmd << _T("something") << variable << _T("something")


and I was wondering...

Why not store those commands in a hash table? Templated, that is. Like:

Code Select Expand


myhashtable["breakpoint"] = _T("something {$varname} something")


like it's done with the compiler plugin? In this case, $varname would be one of many predefined variables. (Or even better, store those in an XML file! )

I'm sure this would enable us to add support for other debuggers besides gdb.

What do you think?

[mandrav]

Well, I purposely have stalled further improvements on the debugger plugin while waiting for the compiler discussion to start. Many design decisions will affect/apply-to the debugger plugin also so it makes sense to wait...

I'm sure this would enable us to add support for other debuggers besides gdb.

Don't think that this is trivial. From what I recall while researching MS's cdb.exe, it was difficult to even get the current instruction's line number and source file...

[rickg22]

I see... well, it's a start.

Anyway, where's the VC debugger docs?

[mandrav]

Install "Microsoft Debugging Tools for Windows" and you 'll find it there