Hi Anton,
On Mar 18, 2010, at 11:33 AM, Anton Kulchitsky wrote:
> Hi Quicney,
>
> thank you! Oh! I am sorry I missed that in ./configure --help. Does it
> slow library down or put other overhead? Otherwise, I do not understand
> why it is not a default behavior?
Yes, it removes some otherwise valid optimizations that confuse tools
like valgrind.
Quincey
> Thank you again, you helped a lot. I always use valgrind and other
> memory checking tools with my programs and probably cannot work without
> them.
>
> Anton
>
>> Hi Anton,
>>
>> On Mar 17, 2010, at 6:37 PM, Anton Kulchitsky wrote:
>>
>>>
>>> I have got the following diagnostics when run my program with
>>> valgrind. This was generated by H5Dwrite call on array of compound
>>> types. Maybe somebody is familiar with this? It does not seem right!
>>> When I remove writing call, everything is fine.
>>
>> If you are going to use valgrind (or another memory checking tool, like
>> Purify), you should configure the HDF5 distribution with the
>> --enable-using-memchecker flag.
>>
>> Quincey
>
> _______________________________________________
> Hdf-forum is for HDF software users discussion.
> [email protected]
> http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
