dump_segment -as ELEMENT fails to parse ELEMENT with negative array index

[Gary Dixon]

The problem is illustrated by the following dump_segment (ds) command:

ds 247|17240 -as ect_header.count"(-1)"
017240
dump_segment: Code 18. Parsing structure ect_header.count(-1).

The full ect_header structure is properly displayed, including the count(-1) array element.

dump_segment 234 -as stack_header.ect_ptr
000000
  ect_ptr = 247|17240   [pd]>!BBBKXGGNBpjnQH.area.linker
r 08:02 0.208 0 level 2

dump_segment 247|17240 -as ect_header
017240
ect_header                    @ 247|17240
  ect_areap = 247|17170   [pd]>!BBBKXGGNBpjnQH.area.linker, ect_area_size = 1044, count (-1) = 0, count (0) = 39, count (1) = 38,
  count (2) = 1, count (3) through count (5) = 0
  entry_list_ptrs (1)         @ 247|17252
    firstp = 247|17416   [pd]>!BBBKXGGNBpjnQH.area.linker, lastp = 247|20442   [pd]>!BBBKXGGNBpjnQH.area.linker
  entry_list_ptrs (2)         @ 247|17256
    firstp = 247|20406   [pd]>!BBBKXGGNBpjnQH.area.linker, lastp = 247|20406   [pd]>!BBBKXGGNBpjnQH.area.linker
  entry_list_ptrs (3)         @ 247|17262
    firstp = null, lastp = null
  entry_list_ptrs (4)         @ 247|17266
    firstp = null, lastp = null
  entry_list_ptrs (5)         @ 247|17272
    firstp = null, lastp = null
  meters                      @ 247|17276
    total_wakeups = 1, total_wait_wakeups = 1, total_call_wakeups = 0, ittes_tossed = 1
  seed = 4
  flags                       @ 247|17303
    mask_call_count = 0
    OFF: call_priority, wakeup_control_points
  ecit_ptr = 247|17314   [pd]>!BBBKXGGNBpjnQH.area.linker, ecit_lth = 64, r_offset = 190230, r_factor = 10766514273,
  last_fast_channel_events = "000000000000"b3
r 08:03 0.252 0 level 2

Because dump_segment -as uses display services of the probe command, I suspect probe also has this difficulty.

Because the analyze_multics (azm) request display (d) uses the dump_segment_ display capabilities, I suspect azm display request also has this problem.