From: Eero T. <oa...@he...> - 2024-10-13 19:19:43
|
Hi, On 12.3.2024 10.44, Thorsten Otto wrote: > On Montag, 11. März 2024 21:15:42 CET Miro Kropáček wrote: >> Having the insane (for Atari world) amounts of RAM in TT/CT60/V4S/Aranym, >> this could work well on our systems, too: >> https://www.phoronix.com/news/Linux-Tracing-Post-Reboots. Long before that (by ~20 years), Linux kernels have had ability to dump similar things to a specific "oops" partition on the disk: https://github.com/torvalds/linux/blob/master/drivers/mtd/mtdoops.c > For aranym atleast, that wont work since the memory may already be cleared by > the host. Also that assumes that we have some backtrace ability in the kernel, > which isn't the case. If you have backtrace ability, like Hatari debugger has (with symbols loaded and profiling enabled), one can just print the backtrace when things crash. There's no need to reboot to working config and printing things from inside the emulation. But on real HW, saving other things than backtrace (regs etc) to reboot-safe buffer might also be useful. - Eero |