[PD-dev] flext or readanysf SIGABRT
Georg Holzmann
grhPD at gmx.at
Mon Aug 29 10:32:08 CEST 2005
Hallo!
unfortunately still the same behaviour (compiled now pd0.39-test7 and
recompiled flext and readanysf)
LG
Georg
>>Program received signal SIGSEGV, Segmentation fault.
>>[Switching to Thread -1209653568 (LWP 29931)]
>>pd_free (x=0xb7f98218) at m_pd.c:29
>>29 if (c->c_freemethod) (*(t_gotfn)(c->c_freemethod))(x);
>>(gdb) bt
>>#0 pd_free (x=0xb7f98218) at m_pd.c:29
>>#1 0xb6d0a2d9 in ~flext_base_shared (this=0x81a8e8c) at
>>source/flext.cpp:85 #2 0xb6d0b8a7 in ~flext_dsp_shared
>>(this=0x81a8e8c) at source/fldsp.cpp:74 #3 0xb6d45040 in
>>readanysf::~readanysf () from /usr/lib/pd/externs/readanysf~.pd_linux
>
> this is while freeing the proxy objects for the inlets ..
>
>
>>anyway, if I only make 3 readanysf~ in an empty patch, and then
>>delete them, I get the following messages:
>
> hm ... something, thomas should have a look at ...
>
>
>>what is maybe important:
>>I use pd0.39-0test6, but had to compile against the header files of
>>pd-0.38-4 (because of the "template" stuff ...)
>
> flext is using private headers that changed from 0.38 to 0.39.
>
> you cannot expect flext / flext externals to work if compiled against
> the wrong headers... i'm about 99% sure, that it's related to that ...
More information about the Pd-dev
mailing list