Debug/ inspect array

[BubikolRamios]

When moving , at debug, onto array , yellow window pops up with elements of array
at end of that (reachable by using vertical scroll bar), if list big enough," : ,...)"

I suggest that would be extended with something like " n elements of x displayed" or like "500 of 3000" or ....

Was looking a while at end of list, being certain that I'm looking at last elements themselves.

[Martin_fr]

This is solely to increase the visibility of the "missing elements" marker?

Because the total count of elements in the array is displayed at the start of the array (configurable in Tools > Options > Debugger > Display Format / at least with FpDebug).

And the total amount of shown (the cut off point) is fixed to 512, though that number is not displayed. Well, "fixed" => configured.
With FpDebug: Tools > Options > Debugger Backend: then look in the property grid for "MemLimits" > "MaxArrayLen" and "MaxStackArrayLen" https://wiki.freepascal.org/LazDebuggerFp

There is some config for gdb based debugger too, you need to look through the property list if you need it.

Be aware, that at least for local vars (MaxStackArrayLen) they are NOT always initialized. They are not initialized on the "begin" line of the proc/func. (that never matters to your code, but you can see it sometimes in the debugger). If paused there, then - if unlucky - the array could have billions of entries. So you do want (actually need) some limit there.


About the visibility, I can see your point. But I am also font of the short nonintrusive "..." form. In older Lazarus, using GDB the raw GDB output was shown, and contained something like "n elements missing" or similar (IIRC).

Of course, something can be added back. Not sure of the text. "x out of y" is informative, but repeats the length info at the start, and conflicts with user settings, if the user disabled that. Though of course, if the user disabled the upfront length, then the "x out of y" can be omitted too, even if that should have its own options....

Alternative, it could be ", {stopped after x elements}" or ", {x elements omitted}"

You can add this as a feature request to our bug tracker. (It will likely be a while before I get to that).
Please make sure to point out, that this is to increase visibility of omitted values.


More important might be a smarter word wrap for the hint.

I have to admit, I myself don't use the hint that often (I prefer the watch window, especially for structures and arrays). Hence, the hints had less attention to detail, yet.