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

David Moore wrote:
> 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.

AFAIU it's possible to annotate such code to avoid valgrind's false 
positive noise.  But I have no idea how intrusive that would be to 
libdc1394's source code.  (Less noise in runtime debug output, more 
noise in the code...)
--

-- 
Stefan Richter
-=====-==--= =--- --==-
http://arcgraph.de/sr/

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july