Author Topic: Debugging Tips / GUI GDB?  (Read 17155 times)

evolutional

  • Guest
Debugging Tips / GUI GDB?
« on: February 10, 2005, 11:47:03 am »
Hey,

Been playing around with CodeBlocks after you advertised it on Gamedev.net, I must say that I'm impressed so far.

One thing I'm having problems with is the debugging support, mainly there's no graphical front-end to GDB!

Will you be looking to implement such a feature (a la Visual Studio)?

prr

  • Guest
Re: Debugging Tips / GUI GDB?
« Reply #1 on: February 10, 2005, 12:42:33 pm »
Quote from: evolutional
One thing I'm having problems with is the debugging support, mainly there's no graphical front-end to GDB!


There are several graphical front-ends for GBD.
AFAIK most populars under *nix are ddd and insight.

If u are looking for a graphical front-end under windows I suggest u to use the excellent and always updated cygwin build of insight.

walter

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Re: Debugging Tips / GUI GDB?
« Reply #2 on: February 10, 2005, 03:49:51 pm »
Quote from: evolutional
One thing I'm having problems with is the debugging support, mainly there's no graphical front-end to GDB!

Will you be looking to implement such a feature (a la Visual Studio)?

Never used VisualStudio  :roll:

GDB support is there, although a bit rudimentary. The debugger plugin will get the development focus it needs after the next release (if not earlier :wink: ).

If you 're asking for something specific, please clarify.

Cheers,
Yiannis.
Be patient!
This bug will be fixed soon...

mike

  • Guest
Debugging Tips / GUI GDB?
« Reply #3 on: February 10, 2005, 04:17:51 pm »
Quote
Never used VisualStudio


:-)
That's why the project files for C::B are called ".dsp" and ".dsw" ;-)

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4315
    • Code::Blocks IDE
Debugging Tips / GUI GDB?
« Reply #4 on: February 10, 2005, 05:54:34 pm »
Quote from: mike
Quote
Never used VisualStudio


:-)
That's why the project files for C::B are called ".dsp" and ".dsw" ;-)

...which were contributed by Muhammad Haggag :lol:
Be patient!
This bug will be fixed soon...