[Sound-open-firmware] Questions about the SOF coredump reader

[Paul Olaru]

Figured it out, I had to use the proper version of GCC, now the tool can properly parse panics. Still, I only get this info for actual panic() calls, for exceptions I see that the DSP hangs instead of calling the exception() handler.

From: Paul Olaru
Sent: Wednesday, July 24, 2019 5:36 PM
To: janusz.jankowski at linux.intel.com
Cc: sound-open-firmware at alsa-project.org
Subject: Questions about the SOF coredump reader

I'm trying to diagnose a few issues on the IMX platform and it would be nice if I would be able to interpret panics and exceptions. I have just fixed a minor issue so that the debugfs "exception" entry is correct.

I would like to know if the tool in sof/tools/coredumper/sof-coredump-reader.py is usable for interpreting such dumps and how it should be used. Right now, I have inserted a "panic" call in my code (that makes a dump which seems to be in the proper format), but whenever I try to run this tool on that /sys/kernel/debug/sof/exception file it gets exceptions (one about exccause and, if I remove the corresponding code, it messes up the pathname interpretation too, complaining about UTF-8 being invalid - I suspect wrong offsets?).

So, how is this tool supposed to be used?