Rare iOS Crash Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x00000001187dae3f

Hi anuj_r_shah_07,

I'm having trouble downloading the crash file you provided. The format seems unusual, and I'm wondering if it might have been altered during the upload process. Could you please:

1. Verify the original file format
2. Re-upload the raw crash file

Your assistance in this matter will be greatly appreciated. Thanks!

Albert Pascual 
 Worldwide Developer Relations.

Hi Albert Pascual,

I am unable to upload the .ips file directly here so had changed the extension to .crash. I am copying the data from crash log here as a text file.

Let me know if this works.

I am an encountering a similar issue as well with the same sort of exception. Attached is my ips file. In my case this is occurring on an M4 mini.

Thank you for providing the crash file. It appears that the crash is occurring within your custom module frames in Thread 11. Without symbolizing the frames, it is not possible to identify the specific issue.

Thread 11 name:   Dispatch queue: com.padlocdocks.padlocscan.PLSBarcodeScanner._scanQueue
Thread 11 Crashed:
0   AilaDecoder                   	       0x100e735c4 fxmtbl01 + 40
1   AilaDecoder                   	       0x100e7553c poeeEg02 + 504
2   AilaDecoder                   	       0x100e74f34 poeeEg01 + 60
3   AilaDecoder                   	       0x100dceb44 getSegmentModules + 320
4   AilaDecoder                   	       0x100dcddf4 growFromCenter + 1620
5   AilaDecoder                   	       0x100dcd0a4 asmldc00 + 404
6   AilaDecoder                   	       0x100dec49c lctarf00 + 748
7   AilaDecoder                   	       0x100e700f8 checkFinderPattern + 4324
8   AilaDecoder                   	       0x100e6ea08 detectFinderPattern + 240
9   AilaDecoder                   	       0x100e6e84c dtcsmo00 + 660

We need to symbolize those frames to see where is the crash located. You can either provide the symbol file that matches that build or better yet, symbolize the file and provide me the already symbolized file.

Fully symbolicate the crash report. See Adding Identifiable Symbol Names to a Crash Report. https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report

Match the crash report to a common pattern. Based on the pattern, take specific actions to further investigate the crash. See Identifying the Cause of Common Crashes. https://developer.apple.com/documentation/xcode/identifying-the-cause-of-common-crashes

With a symbolized file, you’ll be able to find out what code is causing the issue and fix it.

Albert Pascual 
 Worldwide Developer Relations.

Hi Peronica,

I've reviewed your crash file, and it's different compared to the one in this thread. To ensure we can provide you with the best possible assistance, I'd recommend starting a new thread specifically for this crash file.

When creating the new thread, please include the following details:

1. A detailed description of the steps you took leading up to the crash.
2. The crash file itself as an attachment. This will allow us to download and analyze it thoroughly.

Starting a new thread will help us keep this issue organized and track our progress effectively.

Also please, symbolicate the crash report. See Adding Identifiable Symbol Names to a Crash Report. https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report

Thanks for your cooperation!

Albert Pascual
  Worldwide Developer Relations.