I've seen the list get screwed up by trying to reissue a transfer before
getting the callback. The list got a circular segment in that case.
Perhaps something like cancelling a transfer followed by freeing it before
getting the callback causes this?
I made a couple of changes to trap this - I'll see if I still have the code
when I get to work.
Orin.
On Thu, Aug 2, 2012 at 6:13 AM, Pete Batard <p...@akeo.ie> wrote:
> On 2012.08.02 13:28, sebasti...@gmx-topmail.de wrote:
> > (gdb) print ((struct usbi_transfer*)0xb6600468)->list
> > $4 = {prev = 0x0, next = 0x0}
>
> This confirms that our list is screwed up and since we don't check for
> the next/prev validity, we end up with a NULL dereference (actually
> NULL-4), hence the crash.
>
> Now we have to find out why one of list_add, list_add_tail, list_del
> results in prev/next being NULL...
>
> 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
>
------------------------------------------------------------------------------
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
