moin João,
Not that I think this will be of much help, but when I had similar flext-related crashes ("free(): invalid pointer") in the past, it turned out to be due to missing initialization code in the constructor. I really don't believe [pool] suffers from this problem (we would have heard about it before now), but cf. my signature :-/
Anyhoo, I found it helped (but didn't solve all problems) to compile the flext externals in "static debug" mode -- of course, this causes some memory bloat and slows things down a bit, but it might get you running on your target architecture...
marmosets, Bryan
On 2010-08-24 11:30:30, João Martins joaomartins@mac.com appears to have written:
Nothing is as simple as it looks, as I'm learning by the minute. With the latest release of Pd, turning off Gem does not allow "pool" to work properly, and I get exactly the same error message. This leads me back to "pool" in itself. Compiling all of "flext" really seems a daunting task, but I think I'll give it a go, if no one comes up with a better suggestion. ;)
Thank you all.
João Martins