[Libwebsockets] lws + libuv ( mac/freebsd ), explicit_vhosts
beetle at gambler.ru
Mon Nov 28 21:42:02 CET 2016
thanx for answers, thats what I thought about libuv. My version of it is
1.10 (seems ok?)
I made new tests. I've switched off SSL, excess protocols, all extensions.
I do not make some connects now, dont create vhosts. I've simplified all
names and parameters. I've built libws with switching off some
And I am still crashing. At first call to
lws_create_vhost( lwscontext, &info ) - gdb backtrace is the same I sent
This is dump of libwebsockets (freebsd, Apple is the same)
[2016/11/28 22:28:27:2159] NOTICE: Initial logging level 7
[2016/11/28 22:28:27:2159] NOTICE: Libwebsockets version: 2.1.0
beetle at B10.1-v2.0.0-188-ge67dfe1
[2016/11/28 22:28:27:2159] NOTICE: IPV6 not compiled in
[2016/11/28 22:28:27:2159] NOTICE: libev support not compiled in
[2016/11/28 22:28:27:2159] NOTICE: libuv support compiled in and enabled
[2016/11/28 22:28:27:2160] NOTICE: Threads: 1 each 13950 fds
[2016/11/28 22:28:27:2161] NOTICE: mem: platform fd map: 111600 bytes
[2016/11/28 22:28:27:2161] NOTICE: Compiled with OpenSSL support
[2016/11/28 22:28:27:2161] NOTICE: SSL disabled: no
[2016/11/28 22:28:27:2161] NOTICE: mem: per-conn: 688 bytes +
protocol rx buf
[2016/11/28 22:28:27:2161] NOTICE: canonical_hostname = B10.1
[2016/11/28 22:28:27:2162] NOTICE: Creating Vhost 'localhost' port 60000, 1
protocols, IPv6 off
After clearing LWS_SERVER_OPTION_EXPLICIT_VHOSTS added two lines
[2016/11/28 22:29:40:3383] NOTICE: Creating Vhost 'default' port 0, 1
protocols, IPv6 off
[2016/11/28 22:29:40:3400] NOTICE: Listening on port 60815
but finally segfault catched us. Seems to be my vhost has some problem.
at this moment I have no more time for experiments, tomorrow will try to
2016-11-27 23:45 GMT+02:00 Andy Green <andy at warmcat.com>:
> On November 28, 2016 4:22:52 AM GMT+08:00, Andy Green <andy at warmcat.com>
> >On November 28, 2016 1:26:18 AM GMT+08:00, Aleksey Zhukovskiy
> ><beetle at gambler.ru> wrote:
> >>1. It there a reason to use libuv/ev for better perfomance at all?
> >Yes, it will use epoll() rather than poll(). If you have many
> >connections, this is faster.
> Well, on bsd, kqueue. Basically libuv has backends for the best native
> event wait on the platform and converts to generic libuv events.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libwebsockets