MACOS Dolphin (Build 5.0-8253) is crashing on import of my Wii's NAND.
My friend's NAND imports fine - so I suspect this crash is due to a problem with my NAND dump. It would be nice if Dolphin didn't crash if a bad NAND is loaded, but instead displayed an error.
Crash Reporter states:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000015b5b7000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
I tried "Wii NAND Extractor" on my NAND
https://sites.google.com/site/parannoyedwii/projects/wii-nand-extractor
NAND Extractor doesn't crash. But it throws up several "Can't open file for writing:" errors during NAND extract.
Fortunately the code for NAND Extractor is provided, this error appears to occur in the "extractFile" function in "nandExtractor.cs" (see attached from link above) as the message aligns with its "catch" call.
Any chance we can get this exception handler added to Dolphin to prevent a crash? Alternatively/additionally I would appreciate any help to dig into why the NAND generates this error hopefully to figure out how to add a recovery algorithm to resurrect the NAND.
Thanks,
Hastyr
My friend's NAND imports fine - so I suspect this crash is due to a problem with my NAND dump. It would be nice if Dolphin didn't crash if a bad NAND is loaded, but instead displayed an error.
Crash Reporter states:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000015b5b7000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
I tried "Wii NAND Extractor" on my NAND
https://sites.google.com/site/parannoyedwii/projects/wii-nand-extractor
NAND Extractor doesn't crash. But it throws up several "Can't open file for writing:" errors during NAND extract.
Fortunately the code for NAND Extractor is provided, this error appears to occur in the "extractFile" function in "nandExtractor.cs" (see attached from link above) as the message aligns with its "catch" call.
Any chance we can get this exception handler added to Dolphin to prevent a crash? Alternatively/additionally I would appreciate any help to dig into why the NAND generates this error hopefully to figure out how to add a recovery algorithm to resurrect the NAND.
Thanks,
Hastyr