Re: [Valgrind-users] unhandled instruction bytes: 0xC5 0xF9 0x6E 0x45

[Danny W. <da...@to...>]

The target machines uses an i5 CPU but the build machine is a core2 duo which is why I chose 'native'.  Not sure that was the right choice but it works (without Valgrind).

I've just tried -march as 'native', 'core2', and 'pentiumpro'.  All have the same result.

(and you are right: the SIGILL handler doesn't work)

Danny

On 27/11/2016, at 7:08 PM, Tom Hughes wrote:

> On 27/11/16 10:28, Danny Wilson wrote:
> 
>> The build machine is a core2 duo running 32-bit Centos 6.6 and custom
>> kernel 3.10.
>> 
>> I recompiled the app using --march=native and --march=pentiumpro, but
>> got the same error.
> 
> Don't use -march=native - that is telling the compiler to use everything machine has to offer!
> 
>> I'll try the SIGKILL handler now.
> 
> That is not going to work.
> 
> Tom