Luigi Castelli

I think I found a bug in the function linklist_reverse()

1 - Build a linked list with whatever object or custom struct you like.

Flags setting don't matter. For the sake of demonstration let's say it's a 7 node linked list.

That's what I used when I found the bug, but it ought to happen with lists of any length.

2 - Call linklist_reverse() TWICE IN A ROW on the list.

You'll see that the first time the function will perform as expected.

However, the second time around the linked list will be destroyed.

Only one node will still be part of the list.

I am on a MacBook Pro running Mac OS 10.6.2.

Please, someone confirm that they can reproduce.

1 - Build a linked list with whatever object or custom struct you like.
Flags setting don't matter. For the sake of demonstration let's say it's a 7 node linked list.
That's what I used when I found the bug, but it ought to happen with lists of any length.

2 - Call linklist_reverse() TWICE IN A ROW on the list.
You'll see that the first time the function will perform as expected.
However, the second time around the linked list will be destroyed.
(i.e. pointer references are lost)
Only one node will still be part of the list.

bug-in-ext_linklist-h-api

Could it be fixed for the next SDK revision?

Can someone at C74 confirm?
Could it be fixed for the next SDK revision?

Thanks for the reports. I'm looking into and hope to have a fix for Max 5.1.4.

Thanks for the reports.  I'm looking into and hope to have a fix for Max 5.1.4.


Just to update, this bug is fixed for the upcoming Max 5.1.4 update.

Bug in ext_linklist.h API