User forums > General (but related to Code::Blocks)

Debugger doesn't show certain things

<< < (2/2)

BlueHazzard:
Also if you try the steps it would be great if you could give some feedback, so that i can create a proper tutorial for this...

johne53:

--- Quote from: oBFusCATed on July 30, 2018, 07:10:44 pm ---C::B's integration of the debugger is miles away from the one VS. On windows it is more troublesome than on linux.

--- End quote ---

Gosh that's quite sad... maybe about 10 years ago I made the effort to switch from MSVC to GCC (primarily because it's cross-platform) but I soon gave up when I tried to use the GCC debugger (GDB). Admittedly that was 10 years ago but it was truly dreadful compared to debugging in Visual C++.

The GCC compiler seems to have come a long way since then but from what I've read, GDB still isn't much use as a serious debugging tool  :(

oBFusCATed:
Why do you think GDB is not serious tool? As a pure debugger it is as powerful or sometimes more powerful than the VStudios debugger. The only part lacking is the UI at least in C::B.

johne53:
Here are the main things I remember about using C::B with GDB (keep in mind that this was 10 years ago...) Maybe you can let me know if these issues are solved now..?

1) Starting a debug session seemed to take forever (in C::B on Windows). After trying to launch a debug session it would often be minutes before anything happened (and the more break points I set, the longer it would take to launch).

2) IIRC I couldn't set break points 'on-the-fly' (they all needed to get set before launching GDB). In fact I'm not sure if I could even enable & disable break points on-the-fly.

3) As 51423benam noted earlier, sometimes you couldn't inspect variable values easily (or maybe you could inspect the values but not change them?)

4) You couldn't change the order of execution on-the-fly (e.g. if I stopped at a break point, I couldn't skip a few lines or go back a few lines).

Navigation

[0] Message Index

[*] Previous page