Author Topic: Idea for improving the GDB plugin  (Read 7140 times)

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Idea for improving the GDB plugin
« on: October 31, 2005, 05:08:41 pm »
This idea came to me as I was debugging the debugger (lol :P ) plugin. There's usually the construct
Code
cmd << _T("something") << variable << _T("something")

and I was wondering...

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

Code
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?
« Last Edit: October 31, 2005, 05:10:15 pm by rickg22 »

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: Idea for improving the GDB plugin
« Reply #1 on: October 31, 2005, 10:10:11 pm »
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...

Quote
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...
Be patient!
This bug will be fixed soon...

Offline rickg22

  • Lives here!
  • ****
  • Posts: 2283
Re: Idea for improving the GDB plugin
« Reply #2 on: October 31, 2005, 10:24:54 pm »
I see... well, it's a start.

Anyway, where's the VC debugger docs?

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: Idea for improving the GDB plugin
« Reply #3 on: October 31, 2005, 11:06:30 pm »
Install "Microsoft Debugging Tools for Windows" and you 'll find it there ;)
Be patient!
This bug will be fixed soon...