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

[Tom H. <to...@co...>]

On 29/11/16 09:42, Alex Bligh wrote:

>> On 29 Nov 2016, at 01:29, Danny Wilson <da...@to...> wrote:
>>
>> Hi Alex, rebuilding the standard libraries is a little beyond our scope (and I'd figure it unlikely that such a basic function of the c++ library had a memory leak.  Something like that would be well published).  As Tom pointed out, it could also be from a std template compiled in from my program.
>>
>> Good question now is how to disable generation of the unsupported instructions...
>
> I'm not saying the leak is in the standard library, just that the instructions that are traced are in the standard library. I'm also not saying you necessarily need to recompile (just that recompiling the application won't fix it if the instructions that are problematic are in the standard library) - rather I'm suggesting you attempt to obtain a precompiled version of the standard library for a lesser processor.

Except that much of the C++ standard library is templates that compiles 
as part of his application and not a library in the traditional sense.

> Depending on your distribution, recompilation should actually be pretty trivial. On Debian compatible distros its as simple as getting the source (one command) and using 'debuild'. On RPM distros, from memory you get the srpm and go from there.

No distribution that does precompiled packages is going to have built 
with AVX enabled so trying to recompile distro provided libraries is 
almost certainly a red herring.

Danny - what distro are you using, and what architecture flags are you 
specifying when building your own program?

Tom

-- 
Tom Hughes (to...@co...)
http://compton.nu/