News for hackers. Stuff that matters.

A comment on Using LD_PRELOAD to cheat, inject features and investigate programs (2013).

Re:Using LD_PRELOAD to cheat, inject features and investigat... by timtosi on Monday December 04, 2017 @07:42AM (#15843393)
As C language teacher assistants in Uni, we used LD_PRELOAD during project defences to replace the lib standard malloc by one of our own in order to be sure that students allocated & freed memory correclty. Never saw so much Segmentation faults in such a short time window.
[ Parent | on HN ]
Re:Using LD_PRELOAD to cheat, inject features and investigat... by d33 on Monday December 04, 2017 @04:51PM (#15847879)
How about libdislocator?

https://github.com/mirrorer/afl/tree/master/libdislocator

[ Parent | on HN ]
Re:Using LD_PRELOAD to cheat, inject features and investigat... by jwilk on Tuesday December 05, 2017 @07:25AM (#15851296)
If you can afford rebuilding from source, using AddressSanitizer (perhaps also UndefinedBehaviorSanitizer) should be better at uncovering memory safety bugs than any LD_PRELOAD trick.
[ Parent | on HN ]
Re:Using LD_PRELOAD to cheat, inject features and investigat... by wyldfire on Monday December 04, 2017 @11:57AM (#15845320)
Electric Fence is one such library. [1]

[1] https://elinux.org/Electric_Fence

[ Parent | on HN ]