Date: Thu, 20 Jun 2024 09:42:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 279875] sockstat: segmentation fault Message-ID: <bug-279875-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D279875 Bug ID: 279875 Summary: sockstat: segmentation fault Product: Base System Version: 14.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: kirill@varnakov.com Hi. After upgrade to FreeBSD 14.0 I noticed in /var/log/messages rows like: Jun 20 01:36:14 servername kernel: pid 74752 (sockstat), jid 1, uid 1003: exited on signal 11 (no core dump - other error) Jun 20 01:37:41 servername kernel: pid 75150 (sockstat), jid 1, uid 1003: exited on signal 11 (no core dump - other error) Jun 20 01:38:51 servername kernel: pid 75425 (sockstat), jid 1, uid 1003: exited on signal 11 (no core dump - other error) Jun 20 01:39:15 servername kernel: pid 75587 (sockstat), jid 1, uid 1003: exited on signal 11 (no core dump - other error) Jun 20 01:44:02 servername kernel: pid 76745 (sockstat), jid 1, uid 1003: exited on signal 11 (no core dump - other error) This happens after our script tries to parse sockstat output, but sometime = it crashes. Run sockstat without any arguments give same result. One remark th= at server processes a lot of connections. May be backtrace could help you: Process 46451 stopped * thread #1, name =3D 'sockstat.full', stop reason =3D signal SIGSEGV: inva= lid address (fault address: 0x18) frame #0: 0x00001852b6abe497 sockstat.full`displaysock [inlined] file_compare(a=3D<unavailable>, b=3D0x0000000000000000) at sockstat.c:179:38 (lldb) list (lldb) bt * thread #1, name =3D 'sockstat.full', stop reason =3D signal SIGSEGV: inva= lid address (fault address: 0x18) * frame #0: 0x00001852b6abe497 sockstat.full`displaysock [inlined] file_compare(a=3D<unavailable>, b=3D0x0000000000000000) at sockstat.c:179:38 frame #1: 0x00001852b6abe497 sockstat.full`displaysock [inlined] files_t_RB_FIND(head=3D<unavailable>, elm=3D<unavailable>) at sockstat.c:18= 1:1 frame #2: 0x00001852b6abe48e sockstat.full`displaysock(s=3D0x000026891e269a40, pos=3D40) at sockstat.c:1= 165:10 frame #3: 0x00001852b6abdc10 sockstat.full`display at sockstat.c:1364:3 frame #4: 0x00001852b6abcbd8 sockstat.full`main(argc=3D<unavailable>, argv=3D<unavailable>) at sockstat.c:1577:2 frame #5: 0x0000185ada4cbafa libc.so.7`__libc_start1 + 298 frame #6: 0x00001852b6abb17d sockstat.full`_start at crt1_s.S:83 (lldb) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-279875-227>