|
From: Julian S. <js...@ac...> - 2003-11-03 14:43:36
|
CVS commit by jseward: Merge rev 1.17: Updated FAQ #8, to reflect the fact that we now support a lot of SSE/SSE2 instructions. M +9 -13 FAQ.txt 1.7.2.4 --- valgrind/FAQ.txt #1.7.2.3:1.7.2.4 @@ -153,19 +153,15 @@ ----------------------------------------------------------------- -Q8. My program dies (exactly) like this: +Q8. My program dies, printing a message like this along the way: - REPE then 0xF - valgrind: the `impossible' happened: - Unhandled REPE case + disInstr: unhandled instruction bytes: 0x66 0xF 0x2E 0x5 -A8. Yeah ... that I believe is a SSE or SSE2 instruction. Are you - building your app with -march=pentium4 or -march=athlon or - something like that? If you can somehow dissuade gcc from - producing SSE/SSE2 instructions, you may be able to avoid this. - Some folks have reported that removing the flag -march=... - works around this. - - I'd be interested to hear if you can get rid of it by changing - your application build flags. +A8. Valgrind doesn't support the full x86 instruction set, although it + now supports many SSE and SSE2 instructions. If you know the + failing instruction is an SSE/SSE2 instruction, you might be able + to recompile your program without it by fiddling with the + -march=... flag(s) for gcc. In particular, get rid of + -march=pentium4 or -march=athlon if you can. Either way, let us + know and we'll try to fix it. ----------------------------------------------------------------- |