@[email protected] to Programmer [email protected] • 28 days agorace conditionslemmy.zipimagemessage-square84fedilinkarrow-up1779
arrow-up1779imagerace conditionslemmy.zip@[email protected] to Programmer [email protected] • 28 days agomessage-square84fedilink
minus-square@[email protected]linkfedilink28•28 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@[email protected]linkfedilink6•28 days agoI have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
minus-square@[email protected]linkfedilink10•28 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.
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.
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.
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