From owner-freebsd-ports-bugs@FreeBSD.ORG Thu Jun 15 11:40:22 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B3FC16A41A for ; Thu, 15 Jun 2006 11:40:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id F081F43D48 for ; Thu, 15 Jun 2006 11:40:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5FBeLs1000235 for ; Thu, 15 Jun 2006 11:40:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5FBeL4E000234; Thu, 15 Jun 2006 11:40:21 GMT (envelope-from gnats) Date: Thu, 15 Jun 2006 11:40:21 GMT Message-Id: <200606151140.k5FBeL4E000234@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: "Thomas Sandford" Cc: Subject: Re: ports/93274: net/nss_ldap: nss_ldap & nss_mysql cause php to segfault X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Thomas Sandford List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jun 2006 11:40:22 -0000 The following reply was made to PR ports/93274; it has been noted by GNATS. From: "Thomas Sandford" To: , Cc: Subject: Re: ports/93274: net/nss_ldap: nss_ldap & nss_mysql cause php to segfault Date: Thu, 15 Jun 2006 12:30:13 +0100 I'm no longer able to reproduce the crash using the "How-To-Repeat" instructions in the bug report. My current setup is: FreeBSD5.4 (with SMP kernel) php 5.1.4, nss_ldap-1.250, openldap-client-2.3.21 [ie only likely significant change is upgrade from 1.239 to 1.250 in nss_ldap]. I'm continuing to have other random apache segfaults that only appear to happen on PHP pages though - whether this is related to this bug or not I don't know. Tracking of the crashes through use of a proxy indicates that the crashes are on legitimate page accesses, not malicious activity [but that they are not reproducible - ie the same page access as segfaulted on one attempt will sail through on another]. -- Thomas Sandford