The code that handled allocatable array had swapped `count` with `upperBound`. This did not get caught earlier as all the example were using 1 as `lowerBound`. Fixes #98166. With the fix in place, the GDB now correctly handles the case pointed in the bug ticket. (gdb) p min::alloc2d $2 = ((0, 0, 0) (0, 0, 0) (0, 0, 0) (0, 0, 0) (0, 0, 0)) (gdb) ptype min::alloc2d type = integer, allocatable (-1:1,-2:2)
2.0 KiB
2.0 KiB