On 2012.05.15 00:54, Xiaofan Chen wrote: > Nothing special to reproduce. You got 50% chance of segfaults running > the same command again and again.
Yeah, I've actually been testing this, and I was able to reproduce it against the benchmark device (haven't tested any other). It seems all that's needed is insisting a bit, though I'm probably closer to 1 in 5 or 6 runs to experience a segfault. So far my investigation seems to indicate that the issue is due to using an invalid dev->parent_dev pointer in the for() loop at line 764 or darwin_usb.c. All I can tell for now is that it doesn't appear to be due to bad init of the parent_dev attribute from core. Could be that we're trying to access unref'd and restroyed parent devices on OS-X, hence the seemingly random outcome. Regards, /Pete ------------------------------------------------------------------------------ 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
