On 2012.06.30 11:33, Xiaofan Chen wrote: > https://libusb.org/ticket/136 > > Not so sure if this is a real bug or not.
I'm hoping it won't be too difficult to confirm with a modified xusb/plain sample that uses the OP's code, but only loops for 100 or 1000 iterations instead of indefinitely, and then calls libusb_exit(). If there's an actual leak, it should be easy to spot. I don't have a clear idea how one is supposed to check for leaks on OS-X though: there seems to be a port of Valgrind [1], which may also be good to have for more than leaks checks but I assume the OP used the leaks [2] command. Regards, /Pete [1] http://valgrind.org/info/platforms.html [2] https://developer.apple.com/library/mac/#documentation/darwin/reference/manpages/man1/leaks.1.html#//apple_ref/doc/man/1/leaks ------------------------------------------------------------------------------ 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/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
