|
From: Karlan M. <kar...@gm...> - 2009-05-07 20:34:30
|
I haven't really taken the time to dig through the source code to verify this however, I have noticed that some programs which segfault run by the kernel fail to do so when run by valgrind, and occasionally gdb. The only thing I can guess off the top of my head is the code running makes bad assumptions, or memory errors, which only fails when that code is non-zero. * So, *that being said I would like to write a patch, for my own use at first, which writes random bits to all memory being initialized (optionally of course). The problem is I don't know where would be the best place to do this? I have absolutely no clue how valgrind implements memory management however I'm assuming I'd only need to add this in two places, the malloc code, and the allocation code for ".text". Let me know your input on the idea, whether postive or negative; I will be targeting gdb after I have added this functionality to valgrind. I feel this will exhibit more "real world entropy", allowing bugs to present themselves more quickly. If someone could kindly point me in the right direction of where to look in the source code it would be greatly appreciated. Thanks, Karlan Mitchell - http://3dstoneage.com - Free open source SMS service |