No custom modules in place. The segmentation fault happens periodically while the server is up and running. As I mentioned in the initial report, I will see jobs that have never released for over a period of time, and these jobs will not die, even after the initial pid has been killed.
In other words, it is reproduced constantly. Although I don't know what is happening to hold the specific jobs in their "open" state. Karyn > Date: 9 May 1999 16:48:59 -0000 > To: apache-bugdb@apache.org, [EMAIL PROTECTED], [EMAIL PROTECTED] > From: [EMAIL PROTECTED] > Subject: Re: os-solaris/4374: [notice] child pid 1525 exit signal > Segmentation Fault (11) > Mime-Version: 1.0 > > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > [If you do not include this Cc, your reply may be ig- ] > [nored unless you are responding to an explicit request ] > [from a developer. ] > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > Synopsis: [notice] child pid 1525 exit signal Segmentation Fault (11) > > State-Changed-From-To: open-feedback > State-Changed-By: lars > State-Changed-When: Sun May 9 09:48:58 PDT 1999 > State-Changed-Why: > > Do you use any custom modules? > Do you know in what situations the segmentation fault > occurs (can you reproduce it)? > > Release-Changed-From-To: version 1.3.4-1.3.4 > Release-Changed-By: lars > Release-Changed-When: Sun May 9 09:48:58 PDT 1999 >
