Date: Thu, 20 Jan 2022 16:55:57 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 261358] ftp/pure-ftpd 1.0.50 SIGSEGV after user login with PostgeSQL backend Message-ID: <bug-261358-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261358 Bug ID: 261358 Summary: ftp/pure-ftpd 1.0.50 SIGSEGV after user login with PostgeSQL backend Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: sunpoet@FreeBSD.org Reporter: ard_1@mail.ru Flags: maintainer-feedback?(sunpoet@FreeBSD.org) Assignee: sunpoet@FreeBSD.org Created attachment 231180 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D231180&action= =3Dedit ftp/pure-ftpd build log The latest version 1.0.50 of the pure-ftpd SIGSEGV on FreeBSD 13-RELEASE-p6 just after a user login when the PostgreSQL is being used as a user database back-end. The same server configuration was working fine with the previous version 1.= 0.49 of the pure-ftpd server. There are some warnings were spotted in the pure-ftpd build log in the sect= ion that corresponds to PostgreSQL module, but I'm not sure if those warning are the real source of those SIGSEGV. I tried to attach the lldb debugger to the pure-ftpd process just before the SIGSEGV and got the following info: ---- (lldb) attach -p 15274 Process 15274 stopped Executable module set to "/usr/local/sbin/pure-ftpd". Architecture set to: x86_64--freebsd13.0. (lldb) continue Process 15274 resuming Process 15274 stopped * thread #1, name =3D 'pure-ftpd', stop reason =3D signal SIGSEGV: invalid = address (fault address: 0x1538) frame #0: 0x000000080177025f libc.so.7`strlen + 31 libc.so.7`strlen: -> 0x80177025f <+31>: movq (%rcx), %rax 0x801770262 <+34>: movq %rax, %rdx 0x801770265 <+37>: notq %rdx 0x801770268 <+40>: addq %r8, %rax (lldb) bt * thread #1, name =3D 'pure-ftpd', stop reason =3D signal SIGSEGV: invalid = address (fault address: 0x1538) * frame #0: 0x000000080177025f libc.so.7`strlen + 31 frame #1: 0x00000000010459ca pure-ftpd`___lldb_unnamed_symbol149$$pure-= ftpd + 42 frame #2: 0x000000000104462c pure-ftpd`___lldb_unnamed_symbol144$$pure-= ftpd + 684 frame #3: 0x0000000001034760 pure-ftpd`___lldb_unnamed_symbol34$$pure-f= tpd + 544 frame #4: 0x0000000001042338 pure-ftpd`___lldb_unnamed_symbol128$$pure-= ftpd + 1048 frame #5: 0x000000000103ddc8 pure-ftpd`___lldb_unnamed_symbol68$$pure-f= tpd + 3816 frame #6: 0x000000000103e917 pure-ftpd`___lldb_unnamed_symbol74$$pure-f= tpd + 903 frame #7: 0x000000000103cbd4 pure-ftpd`___lldb_unnamed_symbol66$$pure-f= tpd + 6276 frame #8: 0x0000000001030922 pure-ftpd ---- but since the executable built from ports doesn't contain any debug symbols this info is merely useless. I need some help in building this port with the debug symbols enabled to be able to trace this issue further. --=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-261358-7788>