Better than a core dump, which is the state of the system when the fault happened, a flight recorder (which is kind of tracer) would prove very helpfull to tell what sequence of actions (ie. function calls, exceptions, ..) brought to this situation.
Provided the system is equipped with some non volatile memory, the content of the flight recorder could be stored continuously, thus enabling the debug of system freeze, which the new diskdump does not address (was not meant to though).
Does anyone of the readers heard about such a tool?
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds