Re: (python), uid 80: exited on signal 11

From: Donn Cave (donn_at_drizzle.com)
Date: 10/30/04 

Date: Sat, 30 Oct 2004 03:54:51 -0000

Quoth Andrew MacIntyre <andymac@bullseye.apana.org.au>:
| On Thu, 28 Oct 2004, Ksenia Marasanova wrote:
|
|> But I am just curious what that signal 11 means.
|
| Near as I can figure (on FreeBSD 4.8), signal 11 is SEGV (segment
| violation).
|
| Did you test the scripts outside the Apache environment? On the face of
| your description, I'd have to say that one of the modules you've added to
| the scripts has a build problem of one sort or another...

If I remember right, the problem seemed to be associated with a
(C) db module. "Python" programs should be pretty safe from memory
access errors like that, but of course a C module is not safe at all.
Could be a build problem, I guess, but I think more likely some
parameter isn't checked properly and when called in an invalid or
unexpected way, that function crashes.

The "kill -l" shell command enumerates the signals, in order
starting with SIGHUP == 1 (or some versions show the number too.)
They're fairly standardized up to SIGUSR2.

        Donn Cave, donn@drizzle.com

Relevant Pages