captures in regex location

Vladimir Sopot jd at
Sat Mar 7 14:22:43 MSK 2009

Вроде вот так -

# gdb /usr/local/nginx/sbin/nginx core.1414
GNU gdb (GDB; openSUSE 11.1)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later < 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show  
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
For bug reporting instructions, please see:

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib64/
Loaded symbols for /lib64/
Reading symbols from /usr/lib64/
Loaded symbols for /usr/lib64/
Reading symbols from /lib64/
Loaded symbols for /lib64/
Reading symbols from /lib64/
Loaded symbols for /lib64/
Reading symbols from /lib64/
Loaded symbols for /lib64/
Reading symbols from /lib64/
Loaded symbols for /lib64/
Reading symbols from /lib64/
Loaded symbols for /lib64/
Reading symbols from /lib64/
Loaded symbols for /lib64/
Reading symbols from /lib64/
Loaded symbols for /lib64/
Core was generated by `nginx: worker process      '.
Program terminated with signal 11, Segmentation fault.
#0  0x000000000040b014 in ngx_rbtree_delete (tree=0x675c88,  
node=0x8afaa0) at src/core/ngx_rbtree.c:211
211	        temp->parent = subst->parent;
(gdb) bt
#0  0x000000000040b014 in ngx_rbtree_delete (tree=0x675c88,  
node=0x8afaa0) at src/core/ngx_rbtree.c:211
#1  0x0000000000414c17 in ngx_expire_old_cached_files (cache=0x675c88,  
n=2, log=0x7d7f38) at src/core/ngx_open_file_cache.c:713
#2  0x0000000000414cdc in ngx_open_file_cleanup (data=0x8db138) at src/ 
#3  0x00000000004047cc in ngx_destroy_pool (pool=0x8da400) at src/core/ 
#4  0x0000000000428bba in ngx_http_request_done (r=0x7e7820, error=0)  
at src/http/ngx_http_request.c:2812
#5  0x000000000042b099 in ngx_http_finalize_request (r=<value  
optimized out>, rc=<value optimized out>) at src/http/ 
#6  0x000000000042ab27 in ngx_http_finalize_request (r=0x7e7820,  
rc=302) at src/http/ngx_http_request.c:1878
#7  0x00000000004263fd in ngx_http_core_generic_phase (r=0x7e7820,  
ph=0x77b410) at src/http/ngx_http_core_module.c:809
#8  0x00000000004225d3 in ngx_http_core_run_phases (r=0x7e7820) at src/ 
#9  0x00000000004226fc in ngx_http_handler (r=0x675c88) at src/http/ 
#10 0x000000000042bf7d in ngx_http_process_request (r=0x7e7820) at src/ 
#11 0x000000000042c5c6 in ngx_http_process_request_headers  
(rev=0x8dac08) at src/http/ngx_http_request.c:1018
#12 0x000000000042cb95 in ngx_http_process_request_line  
(rev=0x7f69711e3c00) at src/http/ngx_http_request.c:828
#13 0x000000000042979a in ngx_http_init_request (rev=0x7f69711e3c00)  
at src/http/ngx_http_request.c:503
#14 0x000000000042995e in ngx_http_keepalive_handler  
(rev=0x7f69711e3c00) at src/http/ngx_http_request.c:2548
#15 0x000000000041f193 in ngx_epoll_process_events (cycle=0x6721c8,  
timer=<value optimized out>, flags=<value optimized out>)
     at src/event/modules/ngx_epoll_module.c:518
#16 0x0000000000417667 in ngx_process_events_and_timers  
(cycle=0x6721c8) at src/event/ngx_event.c:245
#17 0x000000000041ddc6 in ngx_worker_process_cycle (cycle=0x6721c8,  
data=<value optimized out>) at src/os/unix/ngx_process_cycle.c:767
#18 0x000000000041c693 in ngx_spawn_process (cycle=0x6721c8,  
proc=0x41d74f <ngx_worker_process_cycle>, data=0x0,
     name=0x44b4f3 "worker process", respawn=-2) at src/os/unix/ 
#19 0x000000000041d24c in ngx_start_worker_processes (cycle=0x6721c8,  
n=12, type=-2) at src/os/unix/ngx_process_cycle.c:332
#20 0x000000000041e2bf in ngx_master_process_cycle (cycle=0x6721c8) at  
#21 0x0000000000403fc4 in main (argc=<value optimized out>,  
argv=0x7fff79387b08) at src/core/nginx.c:363
(gdb) q
Quitting: You can't do that without a process to debug.

On Mar 6, 2009, at 6:10 PM, Igor Sysoev wrote:

> On Fri, Mar 06, 2009 at 06:05:08PM +0300, Vladimir Sopot wrote:
>> После применения патча (и полной радости по поводу скорости отдачи :)
>> заметил в nginx/logs/error_log что-то нехорошее, но мне непонятное:
>> 2009/03/06 15:58:08 [alert] 6285#0: worker process 30134 exited on
>> signal 11
> Нужно убедиться, что nginx собран с отладочной информацией (-g),
> получить coredump и сделать так:
> gdb nginx nginx.core
> bt
> q
> Вывод прислать мне.
> -- 
> Игорь Сысоев

More information about the nginx-ru mailing list