User forums > Using Code::Blocks
Show local variables in the debugger
Jenna:
--- Quote from: alexchen on August 02, 2013, 10:09:04 pm ---At least we have something to work on. Bugs can be fixed, but lack of functionality needed for a debugger to be useful will cripple the IDE and render it an editor and code compiler, not a debugger. I was frustrated by lack of local variable display window I ended up using gdb directly. Although it is not better but at lease I can go very low level and get the work done.
--- End quote ---
If I remember correctly the crashes came from gdb, if it tries to access not initialized variables.
If this in not fixed in gdb sources, there is no way for the IDE to fix this or even work around it easily.
killerbot:
--- Quote ---If I remember correctly the crashes came from gdb, if it tries to access not initialized variables.
If this in not fixed in gdb sources, there is no way for the IDE to fix this or even work around it easily.
--- End quote ---
If this really is the case, then we should bring the feature back. People might say, hey CB crashes, while it was actually GDB, but then that same remark goes for eg Eclipse and other IDE's.
Next to that, from a programmers view, not initializing your variables, all hell should go loose upon you ;-)
As said, if that is the cause, the good programmers should not be punished.
I will try the patch when updated too, do we have an example code on how to reproduce such crash, will ask a colleague who uses eclipse to reproduce the crash too.
oBFusCATed:
--- Quote from: killerbot on August 03, 2013, 09:45:37 am ---If this really is the case, then we should bring the feature back. People might say, hey CB crashes, while it was actually GDB, but then that same remark goes for eg Eclipse and other IDE's.
--- End quote ---
This is not the case.
--- Quote from: killerbot on August 03, 2013, 09:45:37 am ---Next to that, from a programmers view, not initializing your variables, all hell should go loose upon you ;-)
--- End quote ---
std::vector is always initialized, but after the constructor is called. If you inspect it before the constructor it is not.
--- Quote from: killerbot on August 03, 2013, 09:45:37 am ---Next to that, from a programmers view, not initializing your variables, all hell should go
I will try the patch when updated too, do we have an example code on how to reproduce such crash, will ask a colleague who uses eclipse to reproduce the crash too.
--- End quote ---
Won't happen in Eclipse, they use GDB/mi and probably aren't evaluating all elements, but have limits.
ollydbg:
The bug report and my patch is posted here: GDB crash under Windows, I don't have GDB crash now. :), but GDB devs seems are not interested to fix bugs under Windows. :(
killerbot:
it only occurs on windows ? or also on linux ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version