I’m having trouble debugging crashes on iOS. For some reason, the logs show some red herring like th...

# multiplatform

[Mark]

I’m having trouble debugging crashes on iOS. For some reason, the logs show some red herring like this just before the app freezes:

Can't show file for stack frame : <DBGLLDBStackFrame: 0xb75988140> - stackNumber:3 - name:kfun:kotlin.text.StringBuilder#<init>(kotlin.Int){}. The file path does not exist on the file system: /opt/buildAgent/work/3b4e5b3c1f97a79b/kotlin/libraries/stdlib/native-wasm/src/kotlin/text/StringBuilder.kt

when the actual bug turns out to be some issue with grabbing something from dependency injection, for example. If I go through the threads in the Debug Navigator on XCode, I can get a better idea that way. But why am I not getting a more useful crash log? Should I be doing something with setUnhandledExceptionHook?

[François]

Same thing here, seems to be a bug from kotlin native; I guess it should be asked inside #C7L3JB43G channel.
Just look at the path which contains “native-wasm”, it doesn’t seem right

[Azim Ansari]

StringBuilder.kt problem mostly occurs due to java compatibility. Check your java versions and toolchain.

[François]

Nothing to do with java here.
It’s a Kotlin native bug : The file path does not exist on the file system: -> native-wasm
But we are on an iOS context not Wasm context

[russhwolf]

I believe native-wasm is a shared source set between native and wasm. iOS is included in the native side of that.

[François]

Ask on #C7L3JB43G channel