Thread
Stories related to "Debugging Your Operating System: A Lesson In Memory Allocation" across the full archive.
* [Leak 1](http://notes.secretsauce.net/notes/2015/09/19_debugging-gnu-emacs-memory-leaks-part-1.html)
* [Leak 2](http://notes.secretsauce.net/notes/2015/10/01_debugging-gnu-emacs-memory-leaks-part-2.html)
* [Tools](http://notes.secretsauce.net/notes/2015/10/05_memory-leak-debugging-tools.html)
Relevant excerpt from the changes of the 231 version:
>A new service setting MemoryDenyWriteExecute= has been added, taking a boolean value. If turned on, a service may no longer create memory mappings that are writable and executable at the same time. This enhances security for services where this...
A good rant on debugging a (basic looking!) ops issue that spiralled into systemd-kafka-land. I've got a few timesyncd around here, working without any issue but this does not look too good. :/
The [Twitter thread](https://twitter.com/thatcks/status/1026929126123479040) where the author explores ...
Hey HN – Petr here. I spent 10+ years heading marketing at various companies, from startups to publicly traded, managing €100M+ budgets and teams up to 200 people. The same problem kept recurring: marketing teams lose institutional knowledge when people leave, brand guidelines get ignored under dead...
When a current system (even with hardware-level MTE memory tag expansion) successfully intercepts a Buffer Overflow attack, what is its instinctive reaction? It immediately terminates the program, generates a Crash Log in the background, and might even pop up a notification telling the user, "M...
Probably the best example of the UNIX philosophy I've ever watched. :)