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

show debugger tip under curser when ctrl key is pressed

<< < (4/8) > >>

MortenMacFly:

--- Quote from: ollydbg on December 21, 2010, 06:36:42 am ---Do we need to implement this feature???

--- End quote ---
I'd say no. I don't think this is very intuitive to be honest. When debugging I am very used to see the tooltips as that's the default I want to see in a debugging session. I think forcing the use of control will make this feature pretty much hidden. And the other way round, too: Making this an option would in fact mean nearly nobody will use it. So: What's wrong with showing the tooltips in the debugger session?!

ollydbg:

--- Quote from: MortenMacFly on December 22, 2010, 07:05:10 am ---
--- Quote from: ollydbg on December 21, 2010, 06:36:42 am ---Do we need to implement this feature???

--- End quote ---
I'd say no. I don't think this is very intuitive to be honest. When debugging I am very used to see the tooltips as that's the default I want to see in a debugging session. I think forcing the use of control will make this feature pretty much hidden. And the other way round, too: Making this an option would in fact mean nearly nobody will use it. So: What's wrong with showing the tooltips in the debugger session?!

--- End quote ---
I think the reason is:

1, this way, we can show both tooltip by cc(do not hold ctrl) and tooltip by gdb(hold the ctrl), and they never be conflict.
2, I don't want to gdb to show something when the mouse hover something, especially some complex data structure, this will
    2a: cause gdb to crash when gdb try to evaluate a complex statement( I think ofb has don some thing to debugger_branch in the last patch to forbid get to evaluate a long or multiline statement)
    2b: slow down the debugging stage, I need to wait until something to be shown.
    2c: gdb will crash when showing some uninitialized data. like uninitialized c++ vector, but holding the ctrl will give a change to avoid the crash.


MortenMacFly:

--- Quote from: ollydbg on December 22, 2010, 07:13:38 am ---2, I don't want to gdb to show something when the mouse hover something, especially some complex data structure, this will
    2a: cause gdb to crash when gdb try to evaluate a complex statement( I think ofb has don some thing to debugger_branch in the last patch to forbid get to evaluate a long or multiline statement)
    2b: slow down the debugging stage, I need to wait until something to be shown.
    2c: gdb will crash when showing some uninitialized data. like uninitialized c++ vector, but holding the ctrl will give a change to avoid the crash.

--- End quote ---
Well - what about a toggle-button in the debugger's toolbar then? To globally enable/disable the evaluation of the cursor... In addition the timer when the tooltip kicks in could be increased. Surely crashes should be fixed and not hidden by disabling options. But in fact I never saw the debugger crash with the branch. :shock:

ollydbg:

--- Quote from: MortenMacFly on December 22, 2010, 07:19:05 am ---
--- Quote from: ollydbg on December 22, 2010, 07:13:38 am ---2, I don't want to gdb to show something when the mouse hover something, especially some complex data structure, this will
    2a: cause gdb to crash when gdb try to evaluate a complex statement( I think ofb has don some thing to debugger_branch in the last patch to forbid get to evaluate a long or multiline statement)
    2b: slow down the debugging stage, I need to wait until something to be shown.
    2c: gdb will crash when showing some uninitialized data. like uninitialized c++ vector, but holding the ctrl will give a change to avoid the crash.

--- End quote ---
Well - what about a toggle-button in the debugger's toolbar then?

--- End quote ---
agreed.


--- Quote ---To globally enable/disable the evaluation of the cursor... In addition the timer when the tooltip kicks in could be increased. Surely crashes should be fixed and not hidden by disabling options. But in fact I never saw the debugger crash with the branch. :shock:

--- End quote ---
did you use the gdb pretty printer?
See the post of mine in the gdb (all the test was under Codeblocks, even I use the gdb cvs 20101216, it will still crash)
http://sourceware.org/ml/gdb/2010-10/msg00045.html

Max:

I'd say no. I don't think this is very intuitive to be honest. When debugging I am very used to see the tooltips as that's the default I want to see in a debugging session.
[/quote]

Try to put the cursor, may be as an involuntary action due to mouse moving,  over a std::vector<double> of 50000 elements ...wait and good luck!

Max

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version