Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: Max on August 22, 2006, 10:05:38 am

Title: Bug in Watches window (debuger).
Post by: Max on August 22, 2006, 10:05:38 am
Dear all,

Have a look to the attached image (DebugWin.jpg). I have a struct called Database in which an array of null terminated
strings is initialized in the function InitializeDatabase. In the initialization I wrote 3 null terminated strings: "gedx0307",
"gedx0307" and "END".

During the debugging session if I watch the struct using the "watch under caret" everything is fine. As you can see the 3
strings appear in the right order. But have a look to the main watches window. One of the "gedx0307" is disappered.

continued next message..

[attachment deleted by admin]
Title: Bug in Watches window (debugger). Part 2
Post by: Max on August 22, 2006, 10:12:44 am
I stopped the debugger, then I started a new debugging session. At the same position the result is displayed in the
attached DebugWindump.jpg, in which I added the memory dump window.

I compressed the image to have less than 128 Kb, but it is still readable.

The memory dump window is correct, the "watch under caret" is correct...but now the main wacthe window seems absurd (to me),
or at least not useful.

Hope this help to fix the issue (if any issue exists). If you need more info..let me know

Max


[attachment deleted by admin]
Title: Re: Bug in Watches window (debuger).
Post by: mandrav on August 22, 2006, 11:01:21 am
Please don't start a new topic for the same issue.
Topics merged.
Title: Re: Bug in Watches window (debuger).
Post by: Max on August 22, 2006, 11:58:00 am
Sorry, I started the two topics (two but linked) because it was not possible to attach the two JPG images. The maximum
attachment dimension is 128 Kb for single message. I tried to reply to my first message attaching the second
image but it was refused anyway.

Max
Title: Re: Bug in Watches window (debuger).
Post by: mandrav on August 22, 2006, 12:50:17 pm
The maximum attachment dimension is 128 Kb for single message.

And there are some good reasons for that...

Anyway, your point came across with the first picture. It's a bug in the watches tree optimizations, which skip consequent same values. It's even been reported in the bug tracker but I haven't found the time to fix it yet.
Title: Re: Bug in Watches window (debuger).
Post by: Phatency on August 22, 2006, 02:53:10 pm
Tip: use .png for screenshots and you most likely won't be exceeding the 128 kb limit.