SamuelPerry

I've built a rather complex patch with quite a few moving parts, and it has begun crashing at various points with no discernible pattern that I can see so far. All I have to go on is that in each of the crash reports produced it always crashes on thread 0 when calling libsystem_malloc.dylib (see attached crash reports). Does anyone have any advice/recommended tools that I could use to better track down the issue? So far I've tried running the patch across Max 8.0.8 and 8.1.3 across both Windows and OSX (swapped to OSX as I couldn't work out how to get a similar stack trace in Windows). I'm now trying to remove as much as possible to boil the patch down to perhaps a few objects that reliably reproduce the crash, but beyond this I'm at a bit of a loss...

Max_crash_report4.txt

Max_crash_report5.txt

Max_crash_report6.txt

Max_crash_report7.txt

Max_crash_report8.txt

Max_crash_report9.txt

Max_crash_report10.txt

Max_crash_report11.txt

Max_crash_report12.txt

Max_crash_report13.txt

Max_crash_report14.txt

I've built a rather complex patch with quite a few moving parts, and it has begun crashing at various points with no discernible pattern that I can see so far. All I have to go on is that in each of the crash reports produced it always crashes on thread 0 when calling libsystem_malloc.dylib (see attached crash reports). Does anyone have any advice/recommended tools that I could use to better track down the issue? So far I've tried running the patch across Max 8.0.8 and 8.1.3 across both Windows and OSX (swapped to OSX as I couldn't work out how to get a similar stack trace in Windows). I'm now trying to remove as much as possible to boil the patch down to perhaps a few objects that reliably reproduce the crash, but beyond this I'm at a bit of a loss...
Thanks!


I've built a rather complex patch with quite a few moving parts, and it has begun crashing at various points with no discernible pattern tha

malloc-sigill-crashes-tips-for-finding-the-source-of-the-issue

Malloc SIGILL crashes - tips for finding the source of the issue?