On Monday 13 March 2017 15:24:46 George . wrote: > Hi Valentin, Sorry, I've sent the mail incidentally before I complete it ;) > > > ssl_proxy_cores # ./nginx -V > nginx version: nginx/1.10.3 > built by gcc 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) > built with OpenSSL 1.0.2g 1 Mar 2016 (running with OpenSSL 1.0.2g-fips 1 > Mar 2016) > TLS SNI support enabled > configure arguments: --prefix=/cdn/nginx_ssl_proxy --with-cc-opt='-O0 -g > -ggdb -march=core2' --with-debug --with-http_geoip_module > --with-http_realip_module --with-http_ssl_module > --without-http_charset_module --without-http_ssi_module > --without-http_userid_module --without-http_autoindex_module > --without-http_scgi_module --without-http_uwsgi_module > --without-http_fastcgi_module --without-http_limit_conn_module > --without-http_split_clients_module --without-http_limit_req_module > --with-http_stub_status_module --with-http_v2_module > > > and some variables values : > > > (gdb) p q > $1 = (ngx_queue_t *) 0x3fb0ab0 > (gdb) p * q > $2 = {prev = 0xd3210507e0f72630, next = 0x5f5ded63e9edd904} > (gdb) p h2c->waiting > $3 = {prev = 0x3ac6ea0, next = 0x3fb0ab0} > > > and here is the config > [..]
Unfortunately, backtrace in this case is almost useless. You should enable in-memory debug log: http://nginx.org/en/docs/debugging_log.html Thus it will be possible to trace the events that resulted in segfault. wbr, Valentin V. Bartenev _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel