Author Topic: The tooltips that shows the variable value is cancelled in 7790?  (Read 5400 times)

Offline huzhongshan

  • Multiple posting newcomer
  • *
  • Posts: 109
The tooltips that shows the variable value is cancelled in 7790?
« on: February 26, 2012, 04:32:36 am »
When debug , I found that the mouse pointed the variable , there is no tooltips to show the value in 7790. Is this function cancelled? I search the debug settings , and find a option " require control key to show ....." , I checked it , and pressed control when mouse pointed to the variable , it didnot work.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5234
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The tooltips that shows the variable value is cancelled in 7790?
« Reply #1 on: February 26, 2012, 05:19:48 am »
and find a option " require control key to show ....." , I checked it , and pressed control when mouse pointed to the variable , it didnot work.
Works fine here(I'm using the rev 7790 debugger branch nightly build), can you show us the debugger full log?
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline huzhongshan

  • Multiple posting newcomer
  • *
  • Posts: 109
Re: The tooltips that shows the variable value is cancelled in 7790?
« Reply #2 on: February 26, 2012, 06:03:22 am »
I set a breakpoint , when F8 , it runs to the breakpoint , and I points the variable i ( press control ) , just a tooltip shows " int main:: i" , not the variable value.

Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: F:\SampleCode\teststack\
Adding source dir: F:\SampleCode\teststack\
Adding file: F:\SampleCode\teststack\bin\Debug\teststack.exe
Changing directory to: F:/SampleCode/teststack/.

[debug]PATH=.;D:\CodeBlocks\MingGW\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Broadcom\Broadcom 802.11 Network Adapter\Driver;C:\Program Files\Lenovo\Bluetooth Software\;C:\Program Files\EgisTec BioExcess\;C:\Program Files\Windows Live\Shared;c:\Program Files\EgisTec Port Locker\;D:\Program Files\MySQL\MySQL Server 4.1\bin;D:\nasm;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files\Java\jdk1.6.0_26\bin;D:\Program Files\TortoiseSVN\bin;C:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual Studio\VC98\bin;D:\Google\google_appengine\
[debug]Command-line: D:\CodeBlocks\MingGW\bin\gdb.exe -nx -fullname  -quiet  -args F:/SampleCode/teststack/bin/Debug/teststack.exe
[debug]Working dir : F:\SampleCode\teststack

Starting debugger: D:\CodeBlocks\MingGW\bin\gdb.exe -nx -fullname  -quiet  -args F:/SampleCode/teststack/bin/Debug/teststack.exe
done

[debug]> set prompt >>>>>>cb_gdb:

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints

[debug]Reading symbols from F:/SampleCode/teststack/bin/Debug/teststack.exe...
[debug]done.
[debug](gdb) >>>>>>cb_gdb:
[debug]> show version
[debug]GNU gdb (GDB) 7.2
[debug]Copyright (C) 2010 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "mingw32".
[debug]For bug reporting instructions, please see:
[debug]<http://www.gnu.org/software/gdb/bugs/>.
[debug]>>>>>>cb_gdb:
[debug]> set confirm off

Debugger name and version: GNU gdb (GDB) 7.2

[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set debugevents on
[debug]>>>>>>cb_gdb:
[debug]> set new-console on
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor att
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source D:\CodeBlocks\share\codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> directory F:/SampleCode/teststack/
[debug]>>>>>>cb_gdb:
[debug]> break "F:/SampleCode/teststack/main.cpp:14"
[debug]Breakpoint 2 at 0x4013e4: file F:\SampleCode\teststack\main.cpp, line 14.
[debug]>>>>>>cb_gdb:
[debug]> run
[debug]gdb: windows_init_thread_list

Child process PID: 320

[debug][New Thread 320.0x139c]
[debug]Breakpoint 2, main () at F:\SampleCode\teststack\main.cpp:14
[debug]F:\SampleCode\teststack\main.cpp:14:161:beg:0x4013e4
[debug]>>>>>>cb_gdb:

At F:\SampleCode\teststack\main.cpp:14

[debug]> set debugevents off
[debug]>>>>>>cb_gdb:
[debug]> bt 30
[debug]#0  main () at F:\SampleCode\teststack\main.cpp:14
[debug]>>>>>>cb_gdb:
[debug]> quit

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5234
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: The tooltips that shows the variable value is cancelled in 7790?
« Reply #3 on: February 26, 2012, 06:17:33 am »
1, please use code tage to wrap your log messages.
2, It looks like the variable name you want to show is one in "c/c++'s keyword set", I mean, E.g. if you variable name is "cout", it will skipped by the debugger plugin. But you can still try to see its value by entering the command like "p cout" in the text control of the debugger plugin panel.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12600
    • Travis build status
Re: The tooltips that shows the variable value is cancelled in 7790?
« Reply #4 on: February 26, 2012, 10:31:40 am »
2, It looks like the variable name you want to show is one in "c/c++'s keyword set", I mean, E.g. if you variable name is "cout", it will skipped by the debugger plugin. But you can still try to see its value by entering the command like "p cout" in the text control of the debugger plugin panel.
This is not longer true. I've fixed this bug in rev 7682 and on my machine it works.

huzhongshan: Are you sure you've enabled the 'Evaluate expression under cursor' setting?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline huzhongshan

  • Multiple posting newcomer
  • *
  • Posts: 109
Re: The tooltips that shows the variable value is cancelled in 7790?
« Reply #5 on: February 26, 2012, 01:12:49 pm »
This is not longer true. I've fixed this bug in rev 7682 and on my machine it works.

huzhongshan: Are you sure you've enabled the 'Evaluate expression under cursor' setting?
I am not sure about it . I enabled the setting in earlier version. When I upgrade to the 7790 , I cannot find the setting ( I set it long time ago).  I knew it should be somewhere , but I cannot find it . Where is the setting of 'Evaluate expression under cursor'?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12600
    • Travis build status
Re: The tooltips that shows the variable value is cancelled in 7790?
« Reply #6 on: February 26, 2012, 01:24:31 pm »
Settings->Debugger->GDB Debugger ->Default (or your config)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline huzhongshan

  • Multiple posting newcomer
  • *
  • Posts: 109
Re: The tooltips that shows the variable value is cancelled in 7790?
« Reply #7 on: February 26, 2012, 01:54:15 pm »
Thanks. It works now!