Obfuscation with dynamic libraries

My project has some dynamic libraries, under lib/ folder with extension .dylib. I added this path to libraryjars.

When i try to run code flow that follows this path, I get a fatal error. Pasting the error, can’t paste the full stack trace. Can anyone help me on what to look for here?

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x0000000107a94068, pid=49920, tid=72967

JRE version: OpenJDK Runtime Environment JBR-17.0.5+7-469.71-jcef (17.0.5+7) (build 17.0.5+7-b469.71)

Java VM: OpenJDK 64-Bit Server VM JBR-17.0.5+7-469.71-jcef (17.0.5+7-b469.71, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64)

Problematic frame:

V [libjvm.dylib+0x120068] AccessInternal::PostRuntimeDispatch<G1BarrierSet::AccessBarrier<548964ull, G1BarrierSet>, (AccessInternal::BarrierType)2, 548964ull>::oop_access_barrier(void*)+0x8

Some thread info:

Current thread (0x000000012ec02e00): JavaThread “AWT-EventQueue-0” [_thread_in_vm, id=72967, stack(0x00000002f19d8000,0x00000002f1bdb000)]

Stack: [0x00000002f19d8000,0x00000002f1bdb000], sp=0x00000002f1bd7920, free space=2046k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.dylib+0x120068] AccessInternal::PostRuntimeDispatch<G1BarrierSet::AccessBarrier<548964ull, G1BarrierSet>, (AccessInternal::BarrierType)2, 548964ull>::oop_access_barrier(void*)+0x8
V [libjvm.dylib+0x4bfef4] jni_GetStringUTFChars+0x118
C [libz3java.dylib+0x3804] Java_com_microsoft_z3_Native_INTERNALmkStringSymbol+0x30
j com.microsoft.z3.Native.INTERNALmkStringSymbol(JLjava/lang/String;)J+0
j com.microsoft.z3.Native.mkStringSymbol(JLjava/lang/String;)J+2
j com.microsoft.z3.StringSymbol.(Lcom/microsoft/z3/Context;Ljava/lang/String;)V+7
j com.microsoft.z3.Context.mkSymbol(Ljava/lang/String;)Lcom/microsoft/z3/StringSymbol;+6
j com.microsoft.z3.Context.mkConst(Ljava/lang/String;Lcom/microsoft/z3/Sort;)Lcom/microsoft/z3/Expr;+3

Apologies, its not related to ProGuard, seems like there is a different issue. Didn’t find a close button so leaving this reply.

1 Like