0x0@lemmy.zip to Programmer Humor@programming.dev · 1 month agorace conditionslemmy.zipimagemessage-square86fedilinkarrow-up1874arrow-down125
arrow-up1849arrow-down1imagerace conditionslemmy.zip0x0@lemmy.zip to Programmer Humor@programming.dev · 1 month agomessage-square86fedilink
minus-squarelobut@lemmy.calinkfedilinkarrow-up31·1 month 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-squarejj4211@lemmy.worldlinkfedilinkarrow-up11·1 month 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-squareGagootron@feddit.orglinkfedilinkarrow-up6·1 month agoEven safe rust can do it, if we allow compiler bugs
minus-squareapelsin12@lemm.eelinkfedilinkarrow-up10·1 month agoIve also seen this, but not from js but node
minus-squareVitabytesDev@feddit.nllinkfedilinkarrow-up6·1 month agoI have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
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.