News for hackers. Stuff that matters.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by vsareto on Thursday June 18, 2020 @11:14AM (#23563822)
That reminds me of the time I saw a C# database save function looking at the stack trace to figure out if it had already been called, exiting if it saw itself on the stack.

I mean, it's not wrong, but it is crazy.

Re:Why is there a “V” in SIGSEGV Segmentation Fault? by tonyarkles on Thursday June 18, 2020 @04:55PM (#23567924)
If I recall, I once did something like this in Python that modified variables in its caller. Not for production, just for shits and giggles :D
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by loeg on Thursday June 18, 2020 @06:34PM (#23568897)