User forums > Nightly builds

The 18 December 2010 build (6900) DEBUGGER BRANCH version is out.

<< < (2/4) > >>

midshipracer:
Hello,

Let me start off saying that I love Code::Blocks and I use it in my profession everyday. However, I'm having trouble with this debugger nightly build.

1. It's difficult to instantly determine which button I'm supposed to click with the new artwork for the debug buttons (continue, step over, etc.). The old ones made much more sense.

2. The new watch layout is clunky. I can't seem to find a way to dereference a pointer. This has actually forced me to revert to an older version. It is just unusable.

Thanks,
Kevin

oBFusCATed:

--- Quote from: midshipracer on December 23, 2010, 09:41:43 pm ---1. It's difficult to instantly determine which button I'm supposed to click with the new artwork for the debug buttons (continue, step over, etc.). The old ones made much more sense.

--- End quote ---
You'll get used to them (I was against them too) or better learn the key shortcuts :)


--- Quote from: midshipracer on December 23, 2010, 09:41:43 pm ---2. The new watch layout is clunky. I can't seem to find a way to dereference a pointer. This has actually forced me to revert to an older version. It is just unusable.

--- End quote ---
1. Press "Insert" and add the * before the pointer. Unfortunately it was not working on windows the last time I tried.
2. Right click -> Rename and add the * ....

I can add the dereferencing if it is such an important feature...

killerbot:
just found a debugger bug with the watches. No refresh of values when watch window has been closed in between.

Input :
simple console application , this is the code :

--- Code: ---#include <iostream>


int main()
{
int foo  = 0;
foo = foo + 20;
    std::cout << foo << std::endl;


double result = foo / 1.5;
std::cout << result << std::endl;
    return 0;
}

--- End code ---

put a breakpoint on line "foo = foo + 20;"

Let's start with a happy path :
- start debugger
- when breakpoint hit : watch "foo", and make the watches window visible
- step to next statement ==> foo is nicely updated in the watch window (20)

the BUG path :
- start debugger
- when breakpoint hit : watch "foo", and make the watches window visible (in case not yet watched and visible)
- now close the watch window !!!!!!!!!!!!!
- step to next statement
- make watch window visible again ===> BUG : foo is not updated in the watch window, is still on 0, and not on 20
NOTE : tooltip does show the new value.

So it seems a refresh is not being carried out !!!

oBFusCATed:
Added to the TODO, will look at it tonight, thanks

killerbot:
any news on the above discovered issue ?

EDIT : or other improvements ? If so maybe we can target a new nightly this weekend ?
@Martin : can you perform a merge : trunk -> debug branch

Navigation

[0] Message Index

[#] Next page

[*] Previous page