Okay, upon further looking. What seems to be happening is that the
executables for whysynth or hexter no longer work, BUT I can start the
synths at the command prompt by calling them through DSSI as:
/usr/local/bin/jack-dssi-host whysynth.so
or
/usr/local/bin/jack-dssi-host hexter.so


So the synths in fact DO work, but for a reason I can't understand, due
to my lack of knowledge I would guess, I can't call them with the
executable files that were put in the /usr/bin folder, therefore none of
their shorcuts work.






On Tue, 2010-02-23 at 22:10 -0800, Sean Bolton wrote:
> Hi Patrick,
> 
> On Feb 23, 2010, at 1:03 PM, Patrick Lefebvre wrote:
> > So I'm getting an error with any synth that uses DSSI
> > Always the same.
> >
> > *** glibc detected *** hexter: free(): invalid next size (fast):
> > 0x0832a128 ***
> >
> >
> > *** glibc detected *** whysynth: free(): invalid next size (fast):
> > 0x09c9e128 ***
> >
> > *** glibc detected *** xsynth-dssi: free(): invalid next size (fast):
> > 0x0953d138 ***
> >
> > I'm using FC10.
> > I've installed the front ends and dssi all from sources but it didn't
> > solve it. The programs compile and install fine, but will not run.
> 
> 
> This is the same problem you posted about a month ago, yes?
> It looked at that time that the problem wasn't in the DSSI plugin,
> but rather in jack-dssi-host.  To confirm that, does the error
> happen with a different host (e.g., ghostess or RoseGarden)?
> Were you able to compile jack-dssi-host with '-g' and get a
> backtrace? You might also try running it with MALLOC_CHECK_
> set to 3:
> 
> $ export MALLOC_CHECK_=3
> $ hexter
> 
> and see if that tells us anything.
> 
> HTH,
> 
> -Sean
> 
> 
> 
> 
>