Hi Philippe, >> hmmm ok. >> it seems it can't handle corruptions that nicely: > Not too sure I understand. The below msgs from Valgrind > are indicating (probable/possible) bugs. Apart of reporting > the error, the behaviour is (usually) not influenced too much > (compared to a native execution). malloc-fill might cause > bigger differences, in case non initialised memory is used.
The problem I see is that the stacktraces seem to be incorrect. For example: ==21521== Invalid write of size 1 ==21521== at 0x402A788: memcpy (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==21521== by 0xF867F95: ??? (in /usr/lib/x86_64-linux-gnu/dri/fglrx_dri.so) ==21521== by 0xFFFF1DFFFFFFFFFF: ??? ==21521== by 0xFFFF1EFFFFFFFFFF: ??? ==21521== by 0x1FFFFFFFF: ??? ==21521== by 0x205: ??? ==21521== by 0x200000000: ??? ==21521== by 0x2: ??? ==21521== Address 0x7f19655e45ab is not stack'd, malloc'd or (recently) free'd This happened on a system with an ati card with the fglrx driver. On my laptop with intel video chipset it does not. Hmmm. -- www.vanheusden.com bitcoin account: 14ExronPRN44urf4jqPMyoAN46T75MKGgP msn address: [email protected] ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
