The root debugger collects the outputs from the leaf debuggers and presents you with an aggregated output. In most cases, this aggregation works fine, but it can be an impediment if you want to know the exact output from certain leaf debuggers.
To remedy this, the debugger assigns a unique number (called a message_id) to each aggregated message and saves the message in the message_id_list. You can use the following commands to inspect the message list and expand its entries:
show_aggregated_message_command
: show aggregated message message_id_list
message_id_list
: expression {,...}
The first form of the command displays the aggregated messages in the list whose message IDs match the numbers specified in the message_id_list. The second form displays all the aggregated messages in the list. If no message_id is specified, the debugger shows the most recently added (newest) message.
expand_aggregated_message_command
: expand aggregated message message_id_list
This command expands the specified messages. If no message_id is specified, the debugger expands the most recently added (newest) message.
You can control the length of the message list using the $aggregatedmsghistory debugger variable. If you set this variable to the default (0), the debugger records as many messages as the system will allow.