Re: [libdc] possible corruption of memory...

[David M. <dcm@MIT.EDU>]

On Thu, 2009-08-06 at 19:15 +0900, Samuel Audet wrote:

> generate the following in valgrind (I'm just pasting the summary. The 
> whole default output is around 1500 lines):
> 

It's normal for valgrind to produce a lot of errors because it doesn't
know how to handle ioctls into the kernel.

That said, it's possible there is a memory leak/corruption, it's just
valgrind might not be too helpful.  libefence might work better.

-David