Re: seg faults when running modperl and GD::Graph

[Rafael Caceres <suppressed>]

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
> 
> <Location /perl>
>      SetHandler perl-script
>      PerlResponseHandler ModPerl::Registry
>      Options +ExecCGI
>      PerlOptions +ParseHeaders
> </Location>
> 
> 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
>