Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

moin Conor, On 2007-02-07 01:12:05, Conor J Curran [EMAIL PROTECTED] appears to have written: sounds familiar indeed... have you by any chance tried compiling your external without threads, linking (statically) to libflext-pd_s.a ? I don't know if you need threads or not, but at least that

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

moin Conor, On 2007-02-06 00:50:17, Conor J Curran [EMAIL PROTECTED] appears to have written: Hi Bryan Thanks for the help on this. I added this as you specified above but now when I try to load the patch which contains the external PD crashes. It is somewhat sporadic. I then recompiled a

fluid~ bug (was: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't))

morning all, I take it all back and assert the opposite! Regarding the following fluid~ error: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1210693952 (LWP 24068)] 0xb7dcb589 in free () from /lib/tls/i686/cmov/libc.so.6 (gdb) backtrace #0 0xb7dcb589 in free ()

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

Hola Bryan, sounds familiar indeed... have you by any chance tried compiling your external without threads, linking (statically) to libflext-pd_s.a ? I don't know if you need threads or not, but at least that might narrow down the range of possible error sources... I have not but I was under

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

Hallo, Bryan Jurish hat gesagt: // Bryan Jurish wrote: First, make sure you're not really delete()ing a NULL pointer ;-) That said, I do think we've stumbled onto the same bug, and that there's something going horribly wrong (possibly because of mis-use and/or misunderstanding of flext's

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

: Sat, 3 Feb 2007 10:32:44 +0100 From: Frank Barknecht [EMAIL PROTECTED] Subject: Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't) To: pd-list@iem.at Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Hallo, Bryan Jurish hat gesagt: // Bryan Jurish wrote

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

50 939 02 33 ( in Finland only) tel: +90 533 712 8245 On Feb 3, 2007, at 1:00 PM, [EMAIL PROTECTED] wrote: Message: 8 Date: Sat, 3 Feb 2007 10:32:44 +0100 From: Frank Barknecht [EMAIL PROTECTED] Subject: Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't) To: pd-list

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

On Sat, 2007-02-03 at 10:32 +0100, Frank Barknecht wrote: First, make sure you're not really delete()ing a NULL pointer ;-) That said, I do think we've stumbled onto the same bug, and that there's something going horribly wrong (possibly because of mis-use and/or misunderstanding of

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

Hi Bryan, Thomas, I think I have the same problem as you. My external crashes when I try to delete the object from the canvas i.e when the destructor of my external is called. The BT is #0 0xb7db0334 in free () from /lib/tls/i686/cmov/libc.so.6 #1 0xb72858b1 in operator delete (ptr=0x0)

Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

morning Conor, comments below... On 2007-02-02 23:18:35, Conor J Curran [EMAIL PROTECTED] appears to have written: Hi Bryan, Thomas, I think I have the same problem as you. you have my deepest, most heartfelt sympathy. have a beer. My external crashes when I try to delete the object

[PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't)

morning all, I've been chasing a bug for several weeks now that I just can't seem to get my head around: symptoms are segfaults and complete crashes in pd (v0.40-2 vanilla) on linux/x86 [debian unstable, gcc 4.1.2]. gdb backtraces are available, and I've just recompiled using identical CFLAGS