Setting TCP listener error callback segfaults about cl-async HOT 5 CLOSED

hmm, seems to work now. added new condition for this case, passed to tcp-server's event-cb

from cl-async.

Saw this again, but unable to reproduthe (uhhhhuhuhuh).

from cl-async.

If you want to reproduce, run the tests in x64 linux. Segfaults quite easily. Might be a byte alignment issue somewhere in the bindings? Somehow I doubt it though since it's a simple callback interface, and all the other callbacks work.

Note that setting the error cb on a tcp listener is now disabled until I can figure this out.

from cl-async.

God damnit, not happening anymore...

from cl-async.

YES!! Figured it out. When a evconnlistener fails to bind to an address/port, it returns a null pointer (which I wasn't checking for...) and setting the error handler on that null pointer was causing a segfault.

Now if the listener is null, tcp-server throws a tcp-server-bind-error condition. No more segfaults jumping on the bed.

from cl-async.