[Top][All Lists]
[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: |
Thu, 13 Jul 2006 23:52:54 -0400 |
On Thu, 2006-07-13 at 12:40 -0500, Benjamin Flaming wrote:
> I finally got around to building Om (CVS) again. It compiles without
> complaint, and the engine seems to start just fine:
>
> ----------------------------------------------------------------------
> Enhanced3DNow! detected
> [AlsaMidiDriver] Successfully opened ALSA sequencer.
> [OSC] Started OSC server at osc.udp://bdesk:16180/
> [PreProcessor] Launching thread.
> [PostProcessor] Starting.
> 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
> [LashDriver] Failed to connect to LASH. Session management will not
> function.
> ----------------------------------------------------------------------
>
> Attempting to launch om_gtk produces the following output, however:
>
> ----------------------------------------------------------------------
> [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 15992
> [OSCController] Attaching to engine at osc.udp://bdesk:16180/
> *** 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).
What version do you have?
-DR-