Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 3466 invoked from network); 4 Sep 2007 20:35:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Sep 2007 20:35:18 -0000 Received: (qmail 13187 invoked by uid 500); 4 Sep 2007 20:35:08 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 13170 invoked by uid 500); 4 Sep 2007 20:35:08 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 13159 invoked by uid 99); 4 Sep 2007 20:35:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 13:35:08 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [200.48.17.70] (HELO m1.aasa.com.pe) (200.48.17.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2007 20:35:01 +0000 Received: from [172.16.0.92] (lima92.aasa.com.pe [172.16.0.92]) by m1.aasa.com.pe (8.12.11.20060308/8.12.10/SuSE Linux 0.7) with ESMTP id l84KXO0p020011; Tue, 4 Sep 2007 15:33:24 -0500 Subject: Re: seg faults when running modperl and GD::Graph From: Rafael Caceres Reply-To: rcaceres@aasa.com.pe To: Matt Williamson Cc: modperl@perl.apache.org In-Reply-To: References: Content-Type: text/plain Date: Tue, 04 Sep 2007 15:37:31 -0500 Message-Id: <1188938251.4041.116.camel@rcaceres.aasa.com.pe> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org If you have PHP (with mod_php) enabled on that server, that's the culprit and it can be fixed by compiling PHP without GD support. On Tue, 2007-09-04 at 13:12 -0700, Matt Williamson wrote: > I noticed that my server is segfaulting when I run a script using > GD::Graph > > e.g. > > [Fri Aug 31 09:26:14 2007] [notice] child pid 6385 exit signal > Segmentation fault (11) > [Fri Aug 31 09:26:18 2007] [notice] child pid 6386 exit signal > Segmentation fault (11) > [Fri Aug 31 09:26:23 2007] [notice] child pid 6387 exit signal > Segmentation fault (11) > [Fri Aug 31 09:30:06 2007] [notice] child pid 6394 exit signal > Segmentation fault (11) > [Fri Aug 31 09:30:52 2007] [notice] child pid 6462 exit signal > Segmentation fault (11) > [Fri Aug 31 09:31:01 2007] [notice] child pid 6448 exit signal > Segmentation fault (11) > [Fri Aug 31 09:31:06 2007] [notice] child pid 6463 exit signal > Segmentation fault (11) > > I am running an ex-cgi script under ModPerl::Registry > > > SetHandler perl-script > PerlResponseHandler ModPerl::Registry > Options +ExecCGI > PerlOptions +ParseHeaders > > > I have read some other places on the web about seg faults, suggesting > that it might be conflicts with other modules, e.g. php. However, it > looks pretty clear that it is the GD::Graph that is doing it. > > Has anyone else seen this? Does anyone know how to fix/debug this? I am > going to try running my cgi with the PerlRun to see if that makes a > difference, although I'd prefer to run in modperl if I can. > > Thank you in advance for your help > > Matt > > > !DSPAM:46ddbc27171191804284693! > > > > ________ Information from NOD32 ________ > This message was checked by NOD32 Antivirus System for Linux Mail Servers. > part000.txt - is OK > http://www.eset.com >