Hallo!
I just got the following behaviour with readanysf~ (0.13, flext 0.4.7): I load a file, play it and when I send the stop message I get a segfault.
gdb gives me the following backtrace: #0 0x401adea2 in mallopt () from /lib/tls/libc.so.6 #1 0x401acdcb in free () from /lib/tls/libc.so.6 #2 0x40469d23 in operator delete () from /usr/lib/libstdc++.so.5 #3 0x44015516 in ReadRaw::~ReadRaw () from /usr/lib/pd/extra/readanysf~.pd_linux #4 0x44017659 in readanysf::m_child () from /usr/lib/pd/extra/readanysf~.pd_linux #5 0x44018475 in readanysf::flext_t_m_child () from /usr/lib/pd/extra/readanysf~.pd_linux #6 0x4401f91d in flext_multi::LaunchHelper () from /usr/lib/pd/extra/readanysf~.pd_linux #7 0x40130b63 in start_thread () from /lib/tls/libpthread.so.0 #8 0x4021318a in clone () from /lib/tls/libc.so.6
So it seems to be a threading issue ...
LG Georg
hi georg ...
So it seems to be a threading issue ...
it's not a threading issue, but an operator overloading issue ... the easiest workaround would be to define FLEXT_NOGLOBALNEW when compiling readanysf ...
or you can try to figure out, how the specific memory region that is freed has been allocated ...
cheers ... tim