Changes between Version 1 and Version 2 of Ticket #65407, comment 5


Ignore:
Timestamp:
Sep 9, 2022, 1:49:23 PM (2 years ago)
Author:
kencu (Ken)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #65407, comment 5

    v1 v2  
    33systems < 10.6 don’t have posix_memalign, so I wrote a best-effort workalike using what Tiger and Leopard did have, and put it in legacysupport. It is not the same as what 10.6+ has, though, and it’s possible that is the source of this hang. You might look into the vala code and see if you can try a different workaround for posix_memalign instead.
    44
    5 the other thought is that it has something to do with trying to free to wrong memory, ie a variation on the libstdc++ “unaligned pointer being freed” issue we have not solved yet…
     5the other thought is that it has something to do with trying to free the wrong memory, ie a variation on the libstdc++ “unaligned pointer being freed” issue we have not solved yet…