@[email protected] to Programmer [email protected]English • 6 months ago"No way to prevent this" say users of only language where this regularly happens - 07/01/2024xeiaso.netexternal-linkmessage-square21fedilinkarrow-up160arrow-down115file-text
arrow-up145arrow-down1external-link"No way to prevent this" say users of only language where this regularly happens - 07/01/2024xeiaso.net@[email protected] to Programmer [email protected]English • 6 months agomessage-square21fedilinkfile-text
minus-square@[email protected]linkfedilink27•6 months agoThe trope will be “old” once the mainstream view is no longer that C-style memory management is “good enough”. That said, this particular vulnerability was primarily due to how signals work, which I understand to be kind of unavoidably terrible in any language.
minus-square@[email protected]linkfedilink4•6 months agoA better language wouldn’t have any need to use POSIX signals in this way.
minus-square@[email protected]linkfedilink9•6 months agoI’m not totally clear on why signals are used here in the first place. Arguably most C code doesn’t “need” to use signals in complex ways, either.
The trope will be “old” once the mainstream view is no longer that C-style memory management is “good enough”.
That said, this particular vulnerability was primarily due to how signals work, which I understand to be kind of unavoidably terrible in any language.
A better language wouldn’t have any need to use POSIX signals in this way.
I’m not totally clear on why signals are used here in the first place. Arguably most C code doesn’t “need” to use signals in complex ways, either.