coredump in 1.10.3

[George .]

Hi Maxim

Unfortunately I guess it will be hard to reproduce it quickly  because it
happened on production machine with heavy traffic.
About the gdb warring - it't not a problem: causes because I've copied
binary to folder were we've collected the core itself:


-rwxr-xr-x 1 cdnuser cdnuser  4753416 Mar 13 11:24 nginx
-rw------- 1 cdnuser cdnuser 92971008 Mar 13 10:03 core
-rwxr-xr-x 1 cdnuser cdnuser  4753416 Feb 10 10:42
/cdn/nginx_ssl_proxy/sbin/nginx

diff nginx /cdn/nginx_ssl_proxy/sbin/nginx

On Mon, Mar 13, 2017 at 3:22 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Mon, Mar 13, 2017 at 03:06:17PM +0200, George . wrote:
>
> > Hi all,
> >
> > We've found two different coredumps in production machines running 1.10.3
> > handing ssl and http v2 traffic.
> >
> > Here is the backtrace of version compiles with -O0 -g -ggdb
> >
> >
> >
> > warning: exec file is newer than core file.
> > [New LWP 28665]
> > [Thread debugging using libthread_db enabled]
> > Using host libthread_db library "/lib/x86_64-linux-gnu/
> libthread_db.so.1".
> > Core was generated by `nginx: worker process          '.
> > Program terminated with signal SIGSEGV, Segmentation fault.
> > #0  0x00000000004aeecc in ngx_http_v2_state_window_update
> (h2c=0x32c8aa0,
> > pos=0x31a52fa "", end=0x31a5314 ")�") at src/http/v2/ngx_http_v2.c:2216
> >
> > warning: Source file is more recent than executable.
> > 2216        ngx_queue_remove(q);
>
> Note: the warning here suggests that the core file is from a
> different executable.  The backtrace provided is likely incorrect.
> Try to reproduce the problem with the current executable to get a
> proper backtrace.
>
> It might be also be a good idea to look into "nginx -V" output and
> the configuration (first of all, to make sure there are no 3rd
> party modules used; if there are any - try to reproduce the
> problem without them), as well as to check if you are able to
> reproduce the problem with the latest mainline version.
>
> --
> Maxim Dounin
> http://nginx.org/
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20170313/962be1d7/attachment-0001.html>