Segmentation fault when deserialising on iOS
See original GitHub issueDescribe the bug
When attempting to deserialise some JSON to objects, a segmentation fault occurs when running on iOS (via the iosX64Test
target)
To Reproduce
See https://github.com/kierans/mpp-serialisation for a sample project which reproduces the issue.
Expected behavior
Environment
- Kotlin version:
1.6.20
- Library version:
1.3.2
- Kotlin platforms:
JVM, iOS
- Gradle version:
7.1.1
- IDE version (if bug is related to the IDE):
IntelliJ IDEA 2021.3.3 (Ultimate Edition)
- Other relevant context:
macOS 11.6.3
Xcode 12.5.1 Build version 12E507
Issue Analytics
- State:
- Created a year ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Segmentation Fault 11due to generics
I'm having trouble with a generic inside a framwork that I have. I have 2 class with almost the same thing and 1...
Read more >Segmentation fault: 11 - Cross-reference to module
I'm trying to resolve an Segmentation Fault with Cross-references to modules. Don't know how to make this work. Part of error below:
Read more >cannot deserialize engine and segmentation fault(core ...
Segmentation fault (core dumped). I add some print functions in my code later and I find that this error came out when deserialize...
Read more >[Solved]-C++ Boot serialization cause a segmentation fault ...
Try enabling your compiler's diagnostics. I usually have -Wall -Wextra -pedantic enabled. Also in deserialize you never initialize items to anything.
Read more >Segmentation Fault (SIGSEGV) vs Bus Error (SIGBUS)
SIGSEGV is abbreviation for “Segmentation Violation”. Few cases where SIGSEGV signal generated are as follows, -> Using uninitialized pointer -> ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s definitely not a solution 😅 It just shows that the segment error doesn’t occur in
main
, but only intest
. This is why I was trying to compare kotlin-test vs Kotest, just to try a 3rd environment.Thanks @i-walker. However moving test code into a
main
folder doesn’t seem like a great solution to me. 😄I’m not sure how to continue to debug this.