> On 2012.07.19 21:08, Pete Batard wrote: > I will actually take this opportunity to apologize to the list for > approving the message, before realizing it was being held due to the > size of its attachment, as it may inconvenience some. I have to apologize to the list members for not compressing the log file. Sorry, but I was not aware of the file size.
> If we can't see anything obvious from the log, we should probably aim at > trying to replicate this data flow, to see if this is a data-bound > reproducible situation, or if it's a data independent issue, such as a > an overflow of concurrency issue. Do you want me to send additional log files? Compressed ones of course! It is perhaps easier to find an existing pattern in the communication that causes the segmentation fault. ========= Regards Sebastian ========= ------------------------------------------------------------------------------ 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
