From: Colin Gillespie <C.G<illespie@ne...> - 2004-08-09 16:06:35
I'm running spyce on apache 1.3 using fcgi on a Debian testing=20
machine. I have a large number of pages up using spyce, so I=20
don't think my setup is the problem.
The trouble I'm having is that when running a small script,=20
sypce returns a segmentation fault. Since it's a third party=20
scientific module it's a bit pointless pointing the code down=20
that causes the error. The server logs return
[Mon Aug 9 15:07:08 2004] [error] [client *.*.*.*] FastCGI:=20
incomplete headers (0 bytes) received from server=20
"usr/share/spyce/run_spyceCGI.py" [Mon Aug 9 15:07:08 2004]=20
[warn] FastCGI: (dynamic) server=20
"/usr/share/spyce/run_spyceCGI.py" (pid 8114) terminated due=20
to uncaught signal '11' (Segmentation fault)
The dodgy code in question runs fine under straight python and=20
is being used by a number of other users.
What's the best way to get to the root of the problem? I've=20
tried setting "debug=3D1" in the spyce.conf but I can't find the=20
error log that it generates.