nginx-0.8.53 segfault

[Maxim C.]

# ulimit -c
0
# ulimit -c unlimited
# ulimit -c
unlimited

# /etc/init.d/nginx restart

wait a little for new coredump )
then

# gdb /usr/sbin/nginx /var/spool/nginx/cores/core
GNU gdb (Gentoo 7.2 p1) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/sbin/nginx...(no debugging symbols
found)...done.
BFD: Предупреждение: /var/spool/nginx/cores/core усечён: ожидался размер
ядра файла >= 2099732480, найдено: 357965824.
[New Thread 19472]
Cannot access memory at address 0xa51db648
Cannot access memory at address 0xa51db648
Cannot access memory at address 0xa51db648
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/ld-linux.so.2
Failed to read a valid object file image from memory.
Core was generated by `nginx: worker process                   '.
Program terminated with signal 11, Segmentation fault.
#0  0x08093c37 in ?? ()
(gdb) bt
#0  0x08093c37 in ?? ()
Cannot access memory at address 0xbb587b2c
(gdb)

i think it's consequence of chpax/grsec... btw previous version of nginx
that was installed on my system didn't have this bug. it was 0.7.X
(don't clearly remember)

-- 
Posted via http://www.ruby-forum.com/.