On Mon, Aug 23, 2010 at 08:47:24PM +0100, João Martins wrote: > When I create a "pool" instance and open the help patch and then try to > close it (this is the fastest way to test, since it produces the same output > as putting a fid_class object into the patch), this is what I get at the > terminal console: > > *** glibc detected *** pd: free(): invalid pointer: 0x0a53dd2c *** > ======= Backtrace: ========= > /lib/tls/i686/cmov/libc.so.6[0xb7515704] > /lib/tls/i686/cmov/libc.so.6(cfree+0x96)[0xb75176b6] > /home/user/pd-externals/xsample/xsample.pd_linux(_ZN17flext_root_singledlEPv+0x32)[0xb5b337b4] > /home/user/pd-externals/xsample/xsample.pd_linux(_ZN12flext_single8AtomList4FreeEv+0x25)[0xb5b33975]
I know that one: Isn't it strange that a crash in pool should give an error message about xsample.pd_linux? I don't know the exact reason for this, but a quick fix was to remove xsample.pd_linux when using pool. Of course then you cannot use xsample. :( So the less quick fix for me was to recompile everything related to flext with the newest versions of the sources. Ciao -- Frank _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
