Compile with less processor optimizations, and/or use a newer valgrind. (Might not work if you use precompiled libraries like NVIDIAs OpenGL which uses SSE, which valgrind doesn't support.)
Valgrind CVS does handle SSE/MMX/3dnow.
/ Per Hedbor ()
Previous text:
2003-06-09 18:40: Subject: Re: Post-padding overwritten
Valgrind fails with the error valgrind: the `impossible' happened: unhandled x86 opcode Basic block ctr is approximately 3150000
Compile with less processor optimizations, and/or use a newer valgrind. (Might not work if you use precompiled libraries like NVIDIAs OpenGL which uses SSE, which valgrind doesn't support.)
So I fail back to mtrace() and mpatrol. I run both when starting Hilfe and exiting immediatly. Both shows there are some leaks.
Have you compiled with --with-debug-malloc when you get those leak reports? Pike normally doesn't bother to free everything just before exit since the OS does that anyway, so it only happens when dmalloc or some other special debug modes are used (see DO_PIKE_CLEANUP in global.h).
Additionnaly mpatrol shows the following error several times:
MEMCOPY: memcpy (0x082D6390, 0x082D6714, 0 bytes, 0x00) [-|-|-]
Just a warning about copying a zero length block. Nothing important but I've added a simple check to 7.5 to avoid it.
ERROR: [FREOPN]: memcpy: attempt to perform operation on free memory
Sounds bad, but is this all? It's not much use without a location.
/ Martin Stjernholm, Roxen IS