Re: [liblo] Avoid segfault when receiving port is busy

Hello Steve,

2013/2/14 Stephen Sinclair <rad...@gm...>:
> What segfaults?  It shouldn't.  Isn't the liblo error handler getting
> called?  It should just report an error saying that the port is
> unavailable.
> On Thu, Feb 14, 2013 at 11:26 AM, Alexandre Quessy <ale...@qu...> wrote:
>> When I create a second liblo receiver on the same port, it segfaults.

Oh! It's because I call lo_server_add_method on a NULL lo_server.
So, the lo_err_handler callback doesn't accept a pointer as an
user-defined argument. I cannot pass a pointer this. (I am using C++)
I assume that with a non-threaded server, lo_server_new will return me
a NULL pointer.

What if was using a threaded server?

Thanks!

-- 
Alexandre Quessy
http://alexandre.quessy.net - Artiste en nouveaux médias
http://perte-de-signal.org - Membre de Perte de signal
http://code.sat.qc.ca - Chercheur-développeur SAT