Is there is timetable when this functionality will be available? This is a very important feature supported by Windows Visual Studio, MacOS Xcode, and Eclipse C++. It makes life so much easier to debug at source code level.I think I posted a patch that restores this functionality some times back to this forums. You could apply it yourself.
Is there is timetable when this functionality will be available? This is a very important feature supported by Windows Visual Studio, MacOS Xcode, and Eclipse C++. It makes life so much easier to debug at source code level.No
Where can I find the patch? I assume it requires a rebuild of Codeblocks from source?Is there is timetable when this functionality will be available? This is a very important feature supported by Windows Visual Studio, MacOS Xcode, and Eclipse C++. It makes life so much easier to debug at source code level.I think I posted a patch that restores this functionality some times back to this forums. You could apply it yourself.
Where can I find the patch? I assume it requires a rebuild of Codeblocks from source?For the original version, please search the forums.
This will be a life saver to anyone who is serious in source code level debugging.I doubt it, in the current implementation this will cause only slowness and random crashes...
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.If I remember correctly the crashes came from gdb, if it tries to access not initialized variables.
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.
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.This is not the case.
Next to that, from a programmers view, not initializing your variables, all hell should go loose upon you ;-)std::vector is always initialized, but after the constructor is called. If you inspect it before the constructor it is not.
Next to that, from a programmers view, not initializing your variables, all hell should goWon't happen in Eclipse, they use GDB/mi and probably aren't evaluating all elements, but have limits.
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.
it only occurs on windows ? or also on linux ?Everywhere...
it only occurs on windows ? or also on linux ?On Windows, when pass a long value (this is a random value) to malloc function, it will failed, then GDB crashes, what my patch do is to limit the size passed to malloc function.
+ if (length > local_opts.print_max)
+ length = local_opts.print_max;
So please stay tuned... I'll post here.Here it is, hopefully complete... sorry for the delay.
I'd very much appreciate if you could provide a working patch because using D (rather than C++) I can't see much other than ints and bools.Can you explain what is the problem here? Post a debug log from the debugger?
You failed to say what is the exact problem again.
I don't intend to install a D compiler to check how it works with C::B.
So you'll has to provide a debug log from the debugger or continue to use 10.05... See the debugger setting for an option to enable it.
Thanks so much but I don't intend to become a gdb expert. After all, I'm using an ide to *not* have to take care of stuff like that.I've stopped reading at this sentence, sorry, but you don't want help, just want to use 10.05 forever. If you want any help post a log from the debugger...
All local variable fanatics could checkout r9283 and start complaining that they are slow and cause gdb/c::b crashes.Hi, Obf, good work, I'm enjoying this new feature now. :)
Enjoy.
set print elements 200