On 2012.08.02 11:34, Pete Batard wrote:
> > (gdb) print ctx->flying_transfers
> > $2 = {prev = 0xb660046c, next = 0xb660046c}
>
> Means that our circular list is pointing to itself (empty), so it all
> looks like we got some list deletion between the initial list_empty()
> check [1], that failed (i.e. list was not empty then), and the time we
> call on to list_for_each_entry() (with a list that is now empty).
Disregard.
The above probably means that the list has a single element, rather than
being empty, which
(gdb) print &ctx->flying_transfers
should confirm. If that's the case the address returned should be
different from 0xb660046c/0x8b64a0c.
Sebastian, can you provide the above gdb info for both cases?
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
