Use VM Region Info to Locate the Memory in Your App’s Address Space

Question

Created Sep ’20

Replies 8

Boosts 0

Views 3.3k

Participants 3

Exception Type: EXCBADACCESS (SIGSEGV)
Exception Subtype: KERNINVALIDADDRESS at 0x0000000203cf4d90
VM Region Info: 0x203cf4d90 is not in any region. Bytes after previous region: 609681 Bytes before following region: 32944752
     REGION TYPE                     START - END            [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
     unused shlib _DATA          203c47a28-203c60000       [  97K] rw-/rw- SM=COW ... this process
--> GAP OF 0x2000000 BYTES
     DATACONST                 205c60000-205c73378       [  77K] rw-/rw- SM=COW ...ispatch.dylib

Any ideas / solution?

Boost

Answer 1

DTS Engineer OP

Apple

Sep ’20

Your app is crashing because it’s accessing a rogue pointer. It’s hard to say more without a full crash report. Please post that here.

IMPORTANT Two things:

Before posting your crash report, try to symbolicate it. See Adding Identifiable Symbol Names to a Crash Report. That may yield useful hints as to what’s gone wrong.
Post your crash report as a text attachment so as to avoid clogging up the timeline.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 2

sunilsolanki2304 OP

Sep ’20

attaching crash logs

Crash logs.

0

Answer 3

DTS Engineer OP

Apple

Sep ’20

attaching crash logs

That is a system log, not a crash report. See Acquiring Crash Reports and Diagnostic Logs for information on how to get a crash report.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 4

sunilsolanki2304 OP

Sep ’20

Crash logs.

App Name: Eaton.Mobile.C360.iOS

0

Answer 5

DTS Engineer OP

Apple

Sep ’20

Consider the backtrace of your crashing thread:

Code Block  0   Eaton.Mobile.C360.iOS … patchSymbolPointerTableEntry + 66573028 (HookCoreImportTable.c:76)
1   Eaton.Mobile.C360.iOS … patchSymbolPointerTableEntry + 66573012 (HookCoreImportTable.c:75)
2   Eaton.Mobile.C360.iOS … HookLibraryAddCallback + 66571716 (HookCore.c:211)
3   libdyld.dylib         … 0x1ac347000 + 62484
4   libdyld.dylib         … 0x1ac347000 + 62144
5   Eaton.Mobile.C360.iOS … HookCore_Init + 66571496 (HookCore.c:306)
6   libdyld.dylib         … 0x1ac347000 + 69040
7   libdyld.dylib         … 0x1ac347000 + 8112
8   libdyld.dylib         … 0x1ac347000 + 68572
9   libdyld.dylib         … 0x1ac347000 + 10480
10  libdyld.dylib         … 0x1ac347000 + 67048
11  libdyld.dylib         … 0x1ac347000 + 195940
12  dyld                  … 0x104e58000 + 38908
13  dyld                  … 0x104e58000 + 30068
14  dyld                  … 0x104e58000 + 4696
15  dyld                  … 0x104e58000 + 4152

Frames 15 through 6 are the dynamic linker starting up your app. Frame 5 looks like a library initialiser in your code, that is HookCore_Init, built from HookCore.c, in Eaton.Mobile.C360.iOS, the main app itself. That library looks like it’s doing some scary patching stuff. You’ll need to dig into that code to see what it’s doing and why it’s dereferencing an invalid pointer.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 6

sunilsolanki2304 OP

Sep ’20

We haven't used any HookCore.c class we are using xamarin tool to build the app

0

Answer 7

DTS Engineer OP

Apple

Sep ’20

We haven't used any HookCore.c class we are using xamarin tool to
build the app

In that case I recommend that you escalate it via that tool’s support channel.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

0

Answer 8