|
From: Jo E. S. <jo...@on...> - 2025-09-24 10:27:03
|
On Wed, 24 Sep 2025 00:31:04 +0200, Thorsten Otto via Freemint-discuss <fre...@li...> wrote: >> On Dienstag, 23. September 2025 20:09:55 CEST Jo Even Skarstein via Freemint- >> discuss wrote: >> > You can't do this if you don't have the sources for the crashing >> > program. >> >> Ah ok i thought you were hunting some bug in your program. >> >> What you could eventually do is still try to run the program under the control >> of the debugger, either the new elf version, or maybe even the version 5.1 >> from sparemint. That should give you atleast the opportunity to examine any >> address you want, before the program terminates. This is related to the "crash assistant" I posted about in the alertpipe thread. My idea was to bring up a disassembled text-segment, highlighting the instruction that caused the memory violation. It is not strictly necessary to access the released memory of the crashed process for this, in most cases I know the location of the binary and can just read the file instead. Not yet sure if this is going to happen though - the casual user will not benefit from this and the ones capable of reading disassembled 68k are already perfectly capable of loading the program in TT-Digger or similar themselves. Jo Even |