User forums > Using Code::Blocks

Debugger - Watch as array - Start offset / size limits

(1/1)

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.

mirai:

--- Quote from: BlueHazzard on September 07, 2020, 06:21:21 pm ---What is the error you are getting?
--- End quote ---
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)?

--- End quote ---
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?

--- End quote ---
I'm not that skilled with raw GDB, sorry, I have to look up command reference.

BlueHazzard:

--- Quote ---I don't know yet, I have to run C::B from a terminal and check if there's any output at all.
--- End quote ---
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

Navigation

[0] Message Index