Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@locus.apache.org Received: (qmail 45327 invoked from network); 18 Jan 2007 16:02:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jan 2007 16:02:53 -0000 Received: (qmail 62620 invoked by uid 500); 18 Jan 2007 16:02:58 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 62598 invoked by uid 500); 18 Jan 2007 16:02:58 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 62589 invoked by uid 99); 18 Jan 2007 16:02:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 08:02:58 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [137.65.248.124] (HELO jericho.provo.novell.com) (137.65.248.124) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 08:02:48 -0800 Received: from [137.65.62.53] (jlewis4.provo.novell.com [137.65.62.53]) by jericho.provo.novell.com with ESMTP; Thu, 18 Jan 2007 09:02:11 -0700 Message-ID: <45AF9AB8.5000706@joe-lewis.com> Date: Thu, 18 Jan 2007 09:05:12 -0700 From: Joe Lewis User-Agent: Thunderbird 1.5.0.4 (X11/20060516) MIME-Version: 1.0 To: modules-dev@httpd.apache.org Subject: Re: child pid 4687 exit signal Segmentation fault (11) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Fang Max wrote: > Hi all , > I am now developing a Filter used to parse html file in my group . > The mistake "child pid 4687 exit signal Segmentation fault (11) " > always turn out in error log.is there any one could tell me what that > exact mean It means that the child process of apache had a segmentation fault. > when it could happen It happens when pointers are used in a bad way, most often. There are other ways to get one, but odds are you have a pointer (e.g. a NULL pointer) that isn't properly checked. > and If there is a elegant instace to depend with ,thanks I'm not sure what you mean. Just to debug it : Start apache in a single process mode (apache2ctl -X) and attach a debugger to the process (e.g. gdb in Linux). When the segv occurs, get the backtrace ("bt" in gdb) to see what function was where. That should give you an idea of which function you have used improperly (or if you wrote the function, you at least know where to start looking - ap*log*error functions can help isolate it to a specific line of code.) Joe