Sometimes these crude techniques (not using valgrind) work well enough anyway. Typically the overhead is a few percent or less.
1) # http://udrepper.livejournal.com/11429.html export MALLOC_PERTURB_=$(($RANDOM % 255 + 1)) echo 1>&2 MALLOC_PERTURB_=$MALLOC_PERTURB_ " # $HOME/.bash_profile" 2) export MALLOC_CHECK_=1 # 0: off; 1: announce on stderr; 2: abort echo 1>&2 MALLOC_CHECK_=$MALLOC_CHECK_ " # $HOME/.bash_profile" which handles double free(), single-byte overruns, etc. [Search the 'net for more documentation.] -- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
