Date: Fri, 23 May 2003 20:04:29 +0200 (CEST) From: coolvibe@hackerheaven.org To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/52621: mod_php4 port library clashes/problems with c-client resulting mod_php4/apache and cli to SIGSEGV Message-ID: <200305231804.h4NI4TEG070967@tiamat.ipv6.hackerheaven.org> Resent-Message-ID: <200305231810.h4NIA8ej021355@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 52621 >Category: ports >Synopsis: mod_php4 port library clashes/problems with c-client resulting mod_php4/apache and cli to SIGSEGV >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri May 23 11:10:07 PDT 2003 >Closed-Date: >Last-Modified: >Originator: coolvibe@hackerheaven.org >Release: FreeBSD 4.8-STABLE i386 >Organization: >Environment: System: FreeBSD tiamat.ipv6.hackerheaven.org 4.8-STABLE FreeBSD 4.8-STABLE #6: Thu Apr 10 01:27:38 CEST 2003 root@tiamat.ipv6.hackerheaven.org:/usr/obj/usr/src/sys/TIAMAT i386 >Description: www/mod_php4 port gets in serious trouble when compiled with imap support. The resulting module and cli binary will coredump with a SIGSEGV and die. There are some weirdnesses with OpenSSL too if your c-client library has OpenSSL support. Attacking the php CLI binary with gdb shows that c-client is the cause of this. >How-To-Repeat: Build mod_php4 with IMAP support. >Fix: Avoid building mod_php4 with IMAP support. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305231804.h4NI4TEG070967>