Re: [Valgrind-developers] Valgrind callgrind failure

[Carl L. <ce...@li...>]

Paul:

I have isolated the issue to the statement 

  import numpy as np

in the file bench_hnsw-short.py.  I can reproduce the failure by deleting all of the lines in bench_hnsw-short.py except for "import numpy as np".  I tried to reproduce the issue on X86-64.  It seems to work just fine on X86.  I tried -v with valgrind to see if that gives any hints as to the issue.  Not seeing anything that is helpful.  Not sure if there is some other valgrind debug mode for callgrind that would be insightful.

                       Carl 


On 4/22/24 08:16, Carl Love via Valgrind-developers wrote:
> Paul:
> 
> I do not get the error with --tool=none or with memcheck.  I only seem to see it with callgrind.
> 
>                     Carl 
> 
> On 4/19/24 22:14, Paul Floyd via Valgrind-developers wrote:
>>
>>
>> On 19-04-24 15:33, Carl Love via Valgrind-developers wrote:
>>>
>>> Valgrind developers:
>>>
>>> I ran into an issue with the valgrind callgrind tool running a python AI benchmark:
>>
>> Hi Carl,
>>
>> Do you get the same error with --tool=none (or memcheck)?
>>
>> A+
>> Paul
>>
>>
>> _______________________________________________
>> Valgrind-developers mailing list
>> Val...@li...
>> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
> 
> 
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers