回复: Segmentation fault sometimes

Sergey A. Osokin osa at freebsd.org.ru
Thu Nov 17 14:09:32 UTC 2022


Hi,

On Fri, Nov 11, 2022 at 09:04:44AM +0000, 王 静凯 wrote:
> Hi,
> Sorry I forget the mail I send before.
> Now the core file generate by nginx 1.22.0.
> It is meaningless to run nginx without third-party modules.
> I want to know if  it crash when calling functions in nginx ( not in
> third-party module ) , it is not the problem relate to third-party
> modules?  Or it also be likely to cause by third-party modules?
> 
> The print in gdb with ‘bt’ and ‘info local’:
> ````
> Core was generated by `nginx: worker process                                '.
> Program terminated with signal 11, Segmentation fault.
> #0  0x0000000000464af6 in ngx_log_error_core (level=8, log=0x3f05518, err=<optimized out>, fmt=0x7ffdf20c6124 "") at src/core/ngx_log.c:168
> 
> warning: Source file is more recent than executable.
> 168              log->writer(log, level, errstr, p - errstr);
> Missing separate debuginfos, use: debuginfo-install glibc-2.17-317.el7.x86_64 nss-softokn-freebl-3.34.0-2.el7.x86_64 sssd-client-1.16.0-19.el7.x86_64
> (gdb) bt
> #0  0x0000000000464af6 in ngx_log_error_core (level=8, log=0x3f05518, err=<optimized out>, fmt=0x7ffdf20c6124 "") at src/core/ngx_log.c:168
> #1  0x00000000004873d7 in ngx_memalign (alignment=16, size=4096, log=0x3f05518) at src/os/unix/ngx_alloc.c:65
> #2  0x000000000046508f in ngx_palloc_block (pool=0x4028770, size=72) at src/core/ngx_palloc.c:186
> #3  0x000000000046527f in ngx_palloc_small (align=1, size=<optimized out>, pool=<optimized out>) at src/core/ngx_palloc.c:173
> #4  ngx_palloc (pool=<optimized out>, size=<optimized out>) at src/core/ngx_palloc.c:127
> #5  0x0000000000465342 in ngx_pcalloc (pool=<optimized out>, size=72) at src/core/ngx_palloc.c:302
> #6  0x0000000000554834 in ngx_rtmp_shared_alloc_frame (size=4096, cl=0x402e830, mandatory=0) at ../nginx-rtmp-module/ngx_rtmp_shared_module.c:229
> #7  0x000000000053c134 in ngx_rtmp_live_av (s=0x47d6eb0, h=0x47cee70, in=0x402e830) at ../nginx-rtmp-module/ngx_rtmp_live_module.c:773
> #8  0x000000000053124a in ngx_rtmp_receive_message (s=0x47d6eb0, h=0x47cee70, in=0x402e830) at ../nginx-rtmp-module/ngx_rtmp_handler.c:875
> #9  0x000000000053200e in ngx_rtmp_recv (rev=<optimized out>) at ../nginx-rtmp-module/ngx_rtmp_handler.c:486

It seems like the third-party rtmp module is still there, right?
Is there any chance to switch it off and reproduce the issue?
BTW what's the version of the rtmp module there?

-- 
Sergey A. Osokin



More information about the nginx mailing list