Which Debugger?
Last time I tested, GDB had issues with packed data. That needs to be fixed in gdb (not yet tested gdb 10, but that has other issues)
FpDebug: not sure about 2.0.x
But in trunk it works. Though for the hint, it shortens the embedded arrays.
ForceSize: ($03030300020227DE, $0005020202020003, $0000030000000300, $0000030000000000, nil, nil)
SetMap: {record} (217020505612494814)
QueryMap: {record} (33695710;
(0, 3, 3, {29 more elements}))
BitMap: {record} ((False, True, True, {29 more elements});
(0, 3, 3, {29 more elements}))
A watch on ProcessDeviceMapData.BitMap
DriveMap: (False, True, True, True, True, False, True, True, True, True, {22 more elements})
DriveType: (0, 3, 3, 3, 3, 0, 2, 2, 2, 2, {22 more elements})
And if you enter ProcessDeviceMapData.BitMap.DriveMap you see the data.
You can open ProcessDeviceMapData in "inspect dialog" (afaik Alt F5), then click through the path, and (in latest trunk) hit the "add watch" button.
---
I did recently notice that packed sets do not yet work in FpDebug.