On Tue, 2012-04-17 at 21:55 +0200, Folkert van Heusden wrote: > The problem I see is that the stacktraces seem to be incorrect. gdb unwinder might work better => try with the Valgrind gdbserver (give --vgdb-error=0 arg to Valgrind, and follow instructions to attach gdb, and then 'continue' your process till the error is encountered).
> 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. > ------------------------------------------------------------------------------ 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 Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
