> Thanks for your help, but I don't really understand the part with "coredump"
> and "backtrace"...

1. Recompile nginx with CFLAGS="-g -O0" (for debugging symbols and without compiler optimization). You can just prepend it to your ./configure line.
Before:
../configure --with-debug --with-ipv6 --with-http_flv_module --with-http_mp4_module
After:
CFLAGS="-g -O0" ./configure --with-debug --with-ipv6 --with-http_flv_module --with-http_mp4_module

2. compile nginx with "make" like you always do.

3. create a directory for the core files and make it readable from your workers. For example: mkdir /nginx-core-dumps/ && chmod a+w /nginx-core-dumps/

4. add this to your nginx configuration:
worker_rlimit_core  500M;
working_directory   /nginx-core-dumps/;

5. (install and) start nginx and wait until it crashes. It should have created the core-dump in /nginx-core-dumps/.

6. (install and) start gdb: gdb nginx /nginx-core-dumps/nginx.core

7. within gdb, run the commands "bt" and "backtrace full", followed by a "quit".

8. Post the gdb output on this mailing list, the developers will analyze it then.


I hope I didn't missed anything, but I think this should be it. Example at [1].


[1] http://pastebin.com/raw.php?i=NPjdQcVu



_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx