Dear mod_perl experts:
Collectively, we've been at this for more than two weeks and have searched
various mod_perl archives, all to no avail.
Symptom:
===
SIGSEGV after fork(). Very reproducible. Memory corruption gets moved
around if the codebase changes.
[ SNIP ]
The above
The only other way I can think of to solve this is to send my module list
to this audience. Please find it, attached, with home-grown modules
deleted.
Have you tried debugging the old-fashioned way, i.e. remove things until it
works? That's your best bet. I suspect you will find that you
At 11:44 AM -0600 2/15/02, Fister, Mark wrote:
Dear mod_perl experts:
Collectively, we've been at this for more than two weeks and have searched
various mod_perl archives, all to no avail.
Symptom:
===
SIGSEGV after fork(). Very reproducible. Memory corruption gets moved
around if
On Fri, Feb 15, 2002 at 11:44:03AM -0600, Fister, Mark wrote:
Dear mod_perl experts:
Collectively, we've been at this for more than two weeks and have searched
various mod_perl archives, all to no avail.
Symptom:
===
SIGSEGV after fork(). Very reproducible. Memory
The only other way I can think of to solve this is to send my module
list
to this audience. Please find it, attached, with home-grown modules
deleted.
Have you tried debugging the old-fashioned way, i.e. remove things until
it
works? That's your best bet. I suspect you will find that
On Fri, Feb 15, 2002 at 12:17:07PM -0800, Paul Lindner wrote:
On Fri, Feb 15, 2002 at 11:44:03AM -0600, Fister, Mark wrote:
Dear mod_perl experts:
Collectively, we've been at this for more than two weeks and have
searched
various mod_perl archives, all to no avail.
