From: Nicholas N. <nj...@cs...> - 2007-04-24 23:20:11
|
On Tue, 24 Apr 2007, Jon Schewe wrote: > I'm working with the raw1394 and dc1394 libraries on Linux and the > raw1394 library does something pretty nasty with memory. It converts a > pointer into an int and writes it to a device node and then the kernel > driver stuffs data into that memory address and sends a message back on > the device. Of course valgrind complains that the memory that comes > back is not initialized. Is there a way to tell valgrind to just trust > that the memory passed to that function gets populated correctly? I > looked at creating supression filters, but since it's on the read call, > not the write call, checking each stack trace takes lots of time. What is happening exactly in terms of system calls? That's what Memcheck looks at. For example, after a read() syscall, it will mark the number of read bytes as initialized. Nick |