So then the code should just recognize that the "cpu" value
is beyond the architecture's maximum array index, report the
inconsistency, and "continue" on to the next map?
Well, that's more or less exactly what I did. See attached patch.
/Per
Dave
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility