|
From: Adam D. <am...@st...> - 2003-08-28 19:53:38
|
Valgrinds exits with this message. Anybody know how to work around it? disInstr: unhandled instruction bytes: 0xF 0xE0 0xC1 0xF Illegal instruction Adam |
|
From: Tom H. <th...@cy...> - 2003-08-28 20:35:25
|
In message <098601c36d9e$4de0bbe0$6f00a8c0@linuxberry>
"Adam Doppelt" <am...@st...> wrote:
> Valgrinds exits with this message. Anybody know how to work around it?
>
> disInstr: unhandled instruction bytes: 0xF 0xE0 0xC1 0xF
> Illegal instruction
That's pavgb, which is an SSE instruction, so the answer is the same
as previously - either compile your application without SSE instructions
or, if your application is testing with CPUID, patch valgrind to stop
it claiming SSE support.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Nicholas N. <nj...@ca...> - 2003-10-12 17:44:38
|
On Thu, 28 Aug 2003, Tom Hughes wrote: > > disInstr: unhandled instruction bytes: 0xF 0xE0 0xC1 0xF > > Illegal instruction > > That's pavgb, which is an SSE instruction In case it wasn't announced: I believe this has been fixed in the CVS HEAD, thanks to Dirk Mueller. N |