2012/8/2 <sebasti...@gmx-topmail.de>:
>> On 2012.07.28 12:06, Ludovic Rousseau wrote:
>> You would get more detailed information by rebuilding libusbx with debug
>> info.
> As you suggested, I compiled libusbx with debug info.
Thanks.
> I'd like you to have a final look at the attached backtrace and confirm
> that the segmentation fault is related to a bug in the Omnikey driver.
>
> Please let me know if you need anything else from the backtrace.
The crash occurs in
#0 0x00697e9b in add_to_flying_list (transfer=0xb6600468) at io.c:1185
The source code line is:
if (!timerisset(cur_tv) || (cur_tv->tv_sec > timeout->tv_sec) ||
That is not the first time I see a crash related to the flying list.
It may well be a bug in libusbx.
In gdb can you display the different variables using:
print cur_tv
print cur_tv->tv_sec
print timeout
print timeout->tv_sec
print *transfer
Bye
--
Dr. Ludovic Rousseau
------------------------------------------------------------------------------
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
