Mada Pay stack corruption

Search This thread

wael2

Member
Jan 25, 2021
11
1
Code:
01-05 18:52:38.403 14963 15012 F libc    : stack corruption detected (-fstack-protector)
01-05 18:52:38.403 14963 15012 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 15012 (Thread-4), pid 14963 (om.mada.madapay)
01-05 18:52:38.715 15053 15053 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-05 18:52:38.715 15053 15053 F DEBUG   : Build fingerprint: 'POCO/surya/surya:12/SQ1D.211205.016.A4/XXXXXXXXXX:userdebug/release-keys'
01-05 18:52:38.715 15053 15053 F DEBUG   : Revision: '0'
01-05 18:52:38.715 15053 15053 F DEBUG   : ABI: 'arm64'
01-05 18:52:38.715 15053 15053 F DEBUG   : Timestamp: 2022-01-05 18:52:38.506723971+0300
01-05 18:52:38.715 15053 15053 F DEBUG   : Process uptime: 2s
01-05 18:52:38.715 15053 15053 F DEBUG   : Cmdline: com.mada.madapay
01-05 18:52:38.715 15053 15053 F DEBUG   : pid: 14963, tid: 15012, name: Thread-4  >>> com.mada.madapay <<<
01-05 18:52:38.715 15053 15053 F DEBUG   : uid: 10163
01-05 18:52:38.715 15053 15053 F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
01-05 18:52:38.715 15053 15053 F DEBUG   : Abort message: 'stack corruption detected (-fstack-protector)'
01-05 18:52:38.715 15053 15053 F DEBUG   :     x0  0000000000000000  x1  0000000000003aa4  x2  0000000000000006  x3  000000797e9885b0
01-05 18:52:38.715 15053 15053 F DEBUG   :     x4  0000000000808080  x5  0000000000808080  x6  0000000000808080  x7  8080808080808080
01-05 18:52:38.715 15053 15053 F DEBUG   :     x8  00000000000000f0  x9  0000007aa128e710  x10 0000000000000000  x11 ffffff80fffffbdf
01-05 18:52:38.715 15053 15053 F DEBUG   :     x12 0000000000000001  x13 000000039ee6b175  x14 00173eec88f7c400  x15 0000000000000030
01-05 18:52:38.715 15053 15053 F DEBUG   :     x16 0000007aa1374248  x17 0000007aa134de70  x18 000000797dac6000  x19 0000000000003a73
01-05 18:52:38.715 15053 15053 F DEBUG   :     x20 0000000000003aa4  x21 00000000ffffffff  x22 000000000000000c  x23 000000797b337600
01-05 18:52:38.715 15053 15053 F DEBUG   :     x24 b4000079fae1e380  x25 b400007abc6ab400  x26 000000797e98b000  x27 000000000000000b
01-05 18:52:38.715 15053 15053 F DEBUG   :     x28 000000797e988810  x29 000000797e988630
01-05 18:52:38.715 15053 15053 F DEBUG   :     lr  0000007aa12ff678  sp  000000797e988590  pc  0000007aa12ff6a8  pst 0000000000000000
01-05 18:52:38.715 15053 15053 F DEBUG   : backtrace:
01-05 18:52:38.715 15053 15053 F DEBUG   :       #00 pc 00000000000986a8  /apex/com.android.runtime/lib64/bionic/libc.so (abort+168) (BuildId: 8f390b5620e87572e416c35e50b926d5)
01-05 18:52:38.715 15053 15053 F DEBUG   :       #01 pc 00000000000acc48  /apex/com.android.runtime/lib64/bionic/libc.so (__stack_chk_fail+20) (BuildId: 8f390b5620e87572e416c35e50b926d5)
01-05 18:52:38.715 15053 15053 F DEBUG   :       #02 pc 000000000005c7b4  /data/app/~~e5GnszsSKeSVhNHTkduc7g==/com.mada.madapay-QpZCQ9ErnFnEHqsNKmPCXQ==/base.apk!libmpsdk.so

NOTE: this issue only occurs on Android 12 ROMs, but does not happen with CherishOS or unoffical Evo X builds.
i do not think this sort of bug post belongs here, but i am only wondering why it happens on specific ROMs and not on others.
 

wael2

Member
Jan 25, 2021
11
1
trying on different rom, getting
Code:
01-05 19:42:43.621  4605  4605 F DEBUG   : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x78c281fe4c
now