DieHard

Source code for the second book: https://github.com/gwf/CBofN Use DieHard to avoid crashing newer window managers such as CWM: https://github.com/emeryberger/DieHard

From the The Computational Beauty of Nature: https://github.com/gwf/CBofN If you use CWM as your window manager, it might crash as some of the software only works fine with the bundled FVWM release or TWM. You can use DieHard: https://github.com/emeryberger/DieHard Usage: env LD_PRELOAD=/path/to/DieHard/src/libdiehard.so /path/to/your/binary example: env LD_PRELOAD=$HOME/src/DieHard/src/libdiehard.so $HOME/src/CBofN/bin/mandel Xaos it's a fun software from the 90's, I think today uses QT5 instead of Xaw, but it's virtually the same interface. Another examples would be the ones from the AI Alife Howto's from the 90's. And, finally, there's the uber known Gnuplot, albeit it's from late 80's, but it was widely developed and used in the 90's, and still really powerful to plot from whatever software, as it can use plain text files and you can

Thanks for the clear explanation. Looking at the source code, it looks similar to modern allocators, just without the per-thread heaps. (I think all modern allocators use size-class slab allocators for small objects.) Curiously, I don't think the academic community has much literature on hardened allocators. It's been a while since I've worked in the area, but I wasn't aware of any other than DieHard from 2006 [1]. I did some searched on the ACM Digital Library (I love that it's all free right now so I can easily provide links in forums), and the only other thing I could find was FreeGuard from 2017 [2]. Maybe the issue there is that academics who design memory allocators tend to be on the systems side of CS, and such people tend to use raw performance as a part of the evaluation. Better security for a new thing does not show up in a grap

What a hack! They have an "automatic patch generator" which "fixes" programs with buffer overflows and dangling pointers. (Ref: https://github.com/emeryberger/DieHard/blob/master/docs/pldi...) If a buffer overflow is detected, the code is patched to make the buffer bigger. If a dangling pointer (use after free) is detected, a time delay is inserted so that the buffer is released some time later than the "free" call. That this is useful is a good argument to get out of C/C++ and into Go, or Rust, or just about anything with subscript checking.