Author Topic: Debugger plugin bug?  (Read 3667 times)

Max

  • Guest
Debugger plugin bug?
« on: February 16, 2007, 08:48:19 pm »
Dear All,

I am writing to flag a strange behavior observed during a debugging session using the latest nightly build 
3607 (it says svn 0 but is 3607) and Windows XP SP2.

I am debugging a multi threading application using Win32 Api. It is not simple to explain the bug, so I will use two images.

In the first one you may observe a block of code in which there are two local variables, defined within the block, hThread and index.

During the debugging I found that they are visible on the watch window even outside the block, and that when I change the variable "index" the variable hThread is changed as well (to the same value) in the watch window.

In the first picture you may observe, just after a breakpoints, the watched value of index (set to 121) and hThread (set to 125). In the watch window both variables have the value 121!! Moreover placing the cursor over hThread (in the editor) you get hThread = address 0xdaee40, value 121.

Then I sent an "info local" to gdb. The result is visible in the debugger window. index=121 (OK) hTread=125 (OK now, but it is displayed as 121 in the watch window)!!!!!

Ok. Now observe the second picture. I simply moved the cursor over index. I got index = address 0xdaee40, value 121.
The address of the variable index  and the address of the variable hThread seem the same!!!! 

The "info local" say a different thing. The two variables have the right value!!

So It may be a bug.

Please, can you help me to understand?

Now the pictures

The first one

http://img159.imageshack.us/my.php?image=firstqv1.jpg][IMG]http://img159.imageshack.us/img159/7896/firstqv1.th.jpg

The second one

http://img259.imageshack.us/my.php?image=secondjz4.jpg][IMG]http://img259.imageshack.us/img259/6569/secondjz4.th.jpg



Massimo