On 26/11/16 15:36, Jeffrey Walton wrote:
> On Fri, Nov 25, 2016 at 9:38 PM, Danny Wilson wrote:
>> I am trying to find a memory leak in a large C++ program which utilizes
>> multiple shared libraries.
>>
>> Unfortunately, valgrind fails with "unhandled instruction bytes:
On Fri, Nov 25, 2016 at 9:38 PM, Danny Wilson wrote:
> I am trying to find a memory leak in a large C++ program which utilizes
> multiple shared libraries.
>
> Unfortunately, valgrind fails with "unhandled instruction bytes: 0xC5 0xF9
> 0x6E 0x45"
>
> It says the illegal
I am new. I run valgrind in arm64 server, it show me the information in red,
and then valgrind exit. What problem is it ? Can you tell me how to make
continue to run ( not exit ).
[EIS_IVP][I] temporal_denoise_multi_frame:1885 frame[1]: imgSize / 3 / 2 =
1331712, motionPixNum = 0
Error: The
> Thanks for the response.
>
> It is a huge application, 1.5M lines not including big external dependencies
> like ACE/TAO. Porting over to 64bit mode would probably take months. Any
> other suggestion? Perhaps disabling the generation of the offending AVX
> instructions with some compiler
Hi Tom,
Thanks for the response.
It is a huge application, 1.5M lines not including big external dependencies
like ACE/TAO. Porting over to 64bit mode would probably take months. Any other
suggestion? Perhaps disabling the generation of the offending AVX instructions
with some compiler flag?