@0x0@lemmy.zip to Programmer Humor@programming.dev • 9 days agorace conditionslemmy.zipimagemessage-square90arrow-up1878
arrow-up1878imagerace conditionslemmy.zip@0x0@lemmy.zip to Programmer Humor@programming.dev • 9 days agomessage-square90
minus-square@lobut@lemmy.calinkfedilink32•9 days agoNot a word of a lie, I saw a “segmentation fault” error in JavaScript. Can’t remember how we resolved it, but it did blow my mind.
minus-square@jj4211@lemmy.worldlinkfedilink12•8 days agoTechnically any language runtime can end in a segmentation fault. For some languages, in principle this shouldn’t be possible, but the runtimes can have bugs and/or you are calling libraries that do some native code at some point.
minus-square@VitabytesDev@feddit.nllinkfedilink6•8 days agoI have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
minus-square@burlemarx@lemmygrad.mllinkfedilink1•8 days agoYup, can confirm. We had a wrapper to a C++ library using JNI, so whenever this library crashed so did the entire JVM.
Not a word of a lie, I saw a “segmentation fault” error in JavaScript.
Can’t remember how we resolved it, but it did blow my mind.
Technically any language runtime can end in a segmentation fault.
For some languages, in principle this shouldn’t be possible, but the runtimes can have bugs and/or you are calling libraries that do some native code at some point.
Even safe rust can do it, if we allow compiler bugs
Ive also seen this, but not from js but node
I have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
Yup, can confirm. We had a wrapper to a C++ library using JNI, so whenever this library crashed so did the entire JVM.