Paul Olaru 3ed68f15af panic: Distinguish exceptions from other panics ... On exceptions and panics, the code will reach panic_rewind. That function will, among the other things it needs to do to dump the info, will also dump the exception cause (exccause register). This means that normally coredumps from panics and those from exceptions are indistinguishable. In this commit I reserve the maximum value for exccause (63) to signify that the dump actually came from a panic instead of a hardware exception. The easiest way I could see that would not duplicate code is to simply set the exccause register to this reserved value (otherwise it could be undefined, as it's not initialized at boot). I also update the core dumper tool to use 63 as the value reserved for panics instead of 0 (which is IllegalInstructionCause, a valid hardware exception). Signed-off-by: Paul Olaru <paul.olaru@nxp.com>		2019-08-01 14:17:18 +02:00
..
sof-coredump-reader.py	panic: Distinguish exceptions from other panics	2019-08-01 14:17:18 +02:00
sof-coredump-to-gdb.sh	license: use spdx identifier in shell scripts	2019-06-02 16:38:17 +01:00