om-synth
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Om-synth] Double free or corruption crashes


From: Dave Robillard
Subject: Re: [Om-synth] Double free or corruption crashes
Date: Tue, 18 Jul 2006 21:55:03 -0400

On Tue, 2006-07-18 at 14:30 -0500, Benjamin Flaming wrote:
> On Friday 14 July 2006 12:18 pm, Dave Robillard wrote:
> > On Fri, 2006-07-14 at 01:12 -0500, Benjamin Flaming wrote:
> > > On Thursday 13 July 2006 10:52 pm, Dave Robillard wrote:
> > > > On Thu, 2006-07-13 at 12:40 -0500, Benjamin Flaming wrote:
> > > > > *** glibc detected *** om_gtk: double free or corruption (out):
> > > > > 0xb70f91c8
> > > >
> > > > IIRC this is caused by an old version of liblo (though the "how" part
> > > > is beyond me).
> > > >
> > I remember this happening to someone, but I don't remember why.  Pretty
> > sure it was some kind of liblo version thing.  Maybe try 0.22?  That's
> > what I happen to have on my laptop at the moment...  That
> > lo_send_message_from function that was in the backtrace is new as of
> > 0.23
> 
> Thanks for the help.  Building and running against liblo 0.22 seems to move 
> things a bit further at least.  The Om engine starts as before.  The 
> interface then outputs the following:
> 
> ------------------------------------------------------------
> [GladeFactory] Loading widgets from /home/benji/32bit/share/om/om_gtk.glade
> [Configuration] Unable to open settings file /home/benji/.omgtkrc
> lash_open_socket: could not connect to host 'localhost', service 'lash'
> lash_comm_connect_to_server: could not create server connection
> lash_init: could not connect to server 'localhost' - disabling LASH
> lash_init: LASH_START_SERVER unset, not attempting to start server 
> automatically
> [LashController] Failed to connect to LASH.  Session management will not 
> function.
> [OSCController] Started OSC listener on port 19493
> ------------------------------------------------------------
> 
> At this point, it pops up a "Connecting to Engine" window with the 
> text "Connecting to engine at ...".  After that, the interface repeats the 
> following text indefinitely, once per second:
> 
> ------------------------------------------------------------
> [OSCController] Attaching to engine at osc.udp://bdesk:16180/
> ------------------------------------------------------------

That bdesk bit is suspicious.  It should be using localhost...

You can put bdesk into /etc/hosts (mapped to 127.0.0.1), or make om_gtk
use "localhost".  It's not working because it's not resolving because
your networking setup is screwy somehow, that's for certain.

As for the launch engine button.. well, let's just stick with "don't
push that" ;)

-DR-






reply via email to

[Prev in Thread] Current Thread [Next in Thread]