News:

The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .

Main Menu

Debugger - Watch as array - Start offset / size limits

Started by mirai, September 07, 2020, 10:09:41 AM

Previous topic - Next topic

mirai

I'm trying to inspect a relatively small piece of a huge array and hitting upper limit for start offset  = 32000.
Is this a limitation of C::B or GDB or what?
Currently on 16.01 release.

BlueHazzard

What is the error you are getting?
What is the output of the full debug log (You have to enable it in the debugger settings)?
Have you tried your use case form the console with raw gdb?

oBFusCATed

Does it happen with 20.03 or 17.12. 16.01 is rather old release, newer releases have many of these assertions already fixed.
(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!]

mirai

Quote from: BlueHazzard on September 07, 2020, 06:21:21 PM
What is the error you are getting?
None, C::B just silently resets any start offset greater than 32000 back to this number and displays wrong part of array.

Quote from: BlueHazzard on September 07, 2020, 06:21:21 PM
What is the output of the full debug log (You have to enable it in the debugger settings)?
I don't know yet, I have to run C::B from a terminal and check if there's any output at all.

Quote from: BlueHazzard on September 07, 2020, 06:21:21 PM
Have you tried your use case form the console with raw gdb?
I'm not that skilled with raw GDB, sorry, I have to look up command reference.

BlueHazzard

QuoteI don't know yet, I have to run C::B from a terminal and check if there's any output at all.
There is a tab with the name "debugger log" near the "build messages" tab. There all debugger output gets logged if you enable it in Settings->Debugger->Common->Full Debug log

But as obfuscated pointed out, you should update to at least 20.XX