> The ALSA developers say that this is no problem since ioctl would not > touch the pointer. Is it correct to use ioctl this way?
ioctl() related to "sound" is notoriously murky: poorly documented and a cesspool of partial implementation (many corner cases, unfinished code, tends to work only for the well-worn ruts of common usage.) Notice the "ioctl(generic)": memcheck doesn't even differentiate _which_ ioctl is being used, so memcheck cannot know that this specific case is supposed not to touch a memory region. (The ALSA developers could ameliorate the situation quite easily by passing a pointer to known-initialized memory.) > If yes, can valgrind be instructed to ignore this case? See: $ valgrind --help | grep suppress -- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
