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
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.
Symptom
On Thu, Feb 07, 2002 at 01:03:29AM +, Ged Haywood wrote:
Hi there,
Hi! Thank you SOOO much for the reply!
[SNIP]
You might try usemymalloc.
Tried that. Note: you also tried to help a fellow back in November of
2001 on this VERY same stack trace.
On Thu, Feb 07, 2002 at 09:35:18PM +, Ged Haywood wrote:
Hi there,
On Thu, 7 Feb 2002, Fister, Mark wrote:
Tried that. Note: you also tried to help a fellow back in November of
2001 on this VERY same stack trace.
http://groups.yahoo.com/group/modperl/message/39560
Heh
