At that point your system is to be considered unstable anyway, and the crash log will already have been sent to serial. If you capture it there, you might as well just reboot when you get the requester.Belxjander wrote:To clarify my original request...
1: optional bypass of the *existing* GUI (I refer to the crash requester *BEFORE* GrimReaper launch...)
Again, why not just reboot and be done with it.2: restart or reset of input.device on crash termination
Already done - through serial.3: possibly saving a crashlog (yes this is risky and least implimentable)
I'm pretty sure the vast majority of those who really need crash logs do have at least one other machine capable of the capture. Even a Windows machine or classic Amiga will do (although of course i would be preferable if it has a SilverSurfer or similar fast serial port fitted, and possibly network for easy transfer of the capture file to your main machine).As for the "suggestions" about a second machine...
I'll revisit the idea when I have a second machine
Assumption of a second or other machine is something to query first I believe
BTW, there is another alternative, at least in situations where the crashed machine can be warm booted, and where the crash doesn't bring the system into an endless loop with much debug output. You can set the debug console to memory, and then in your User-Startup (or even Startup-Sequence) have a DumpDebugBuffer CLEAR command with redirection to a file, and maybe a simple rotational backup of that file before the command. That way your crash information is ready and waiting for you on your HD after rebooting. I partly relied on that before I got around to setting up all my serial links.
Best regards,
Niels