[PD-dev] VASP vs plugin~ weirdness

[Michal Seta]

Aw, sorry.

Debian etch.
pd 0.39.2-1 (binary apt-gettable)
vasp v. 0.1.4pre built from CVS (in March, actually, I checked).

I had a similar issue with [pool] (probably around January, February).
Curiously enough, they only interfere with [plugin~].

On the other hand, it could be [plugin~]'s fault :)

Here's a backtrace.  Note, that all I did was run -lib vasp and opened
a new empty window and tried to instantiate [plugin~].  

#0  0xb7dbab81 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/libpthread.so.0
#1  0xb74772fb in flext_multi::ThrCond::Wait ()
   from /usr/local/lib/pd/extra/vasp.pd_linux
#2  0xb747da2a in flext_base_multi::QWorker ()
   from /usr/local/lib/pd/extra/vasp.pd_linux
#3  0xb7476c26 in flext_multi::IsPointer ()
   from /usr/local/lib/pd/extra/vasp.pd_linux
#4  0xb7db8ced in start_thread () from /lib/tls/libpthread.so.0
#5  0xb7d4cdee in clone () from /lib/tls/libc.so.6

./MiS

Thomas Grill <gr at grrrr.org> writes:

> Hi Michal,
> it would be useful to have more detailed information about your
> configuration.
> Platform? PD version? VASP version, downloaded as a package or from CVS?
> greetings,
> Thomas
> 
> Am 10.08.2006 um 07:16 schrieb Michal Seta:
> 
> > Hi all,
> >
> > there is some weirdness happening when VASP is being loaded as -lib
> > (ok, perhaps I shouldn't do such things) and [plugin~] is being used.
> > The combination results in a segfault.  I had exactly the same issue
> > with [pool] a while back (and it was in fact pointed out to me that I
> > should report this to the list but it slipped my brain).
> >
> > ./MiS
> >
> >
> > _______________________________________________
> > PD-dev mailing list
> > PD-dev at iem.at
> > http://lists.puredata.info/listinfo/pd-dev
> >
> >
> 
> Thomas Grill
> http://grrrr.org