News for hackers. Stuff that matters.
Re:Debug Programs by Modifying Them by slaymaker1907 on Tuesday April 27, 2021 @04:43PM (#26961241)
One trick to minimize debugging footprint is to store logs in a ring buffer/array list and defer printing. It's not perfect, but if you use a ring buffer, you can avoid making any syscalls until you are truly ready to print. Thread synchronization can obviously still be a problem, but that can be mitigated by using thread local buffers or by using a lockless ring buffer.

Ring buffers are also nice because you can also use them for cases where you don't normally want some information printed because it would introduce too much overhead, but you want the option to print it out in case of crashes/errors. On an engineering side, you just need to be careful not to put too much through this system so the buffer stays useful and also avoid putting something only in the ring buffer system that should really just be logged normally.

Re:Debug Programs by Modifying Them by nefitty on Wednesday April 28, 2021 @03:04AM (#26966573)
This is genius. I hadn’t heard of this logging style before. I’m going to try it tomorrow morning.
Re:Debug Programs by Modifying Them by pjc50 on Wednesday April 28, 2021 @05:12AM (#26967334)
A variant I developed in an embedded system, which had weirdly defective debugging facilities: define an area of memory which is not cleared on startup. Log into a circular buffer there. On startup, output the contents of the buffer over the serial link (or similar).
Re:Debug Programs by Modifying Them by hyperman1 on Wednesday April 28, 2021 @05:54AM (#26967612)
There are many variants. One is to put the ringbuffer in a shared memory segment or mmapped file, and use another process to read and print the content.