www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From George Planansky <george_planan...@harvard.edu>
Subject Re: mod_perl/4434: on solaris 2.6, apache 1.3.6 dumps core with mod_perl-1.19 DSO
Date Mon, 21 Jun 1999 04:40:00 GMT
The following reply was made to PR mod_perl/4434; it has been noted by GNATS.

From: George Planansky <george_planansky@harvard.edu>
To: ask@apache.org
Cc: apache-bugdb@apache.org, <apbugs@apache.org>
Subject: Re: mod_perl/4434: on solaris 2.6, apache 1.3.6 dumps core with mod_perl-1.19 DSO
Date: Mon, 21 Jun 1999 00:34:06 -0400 (EDT)

 Problem was solved in, and by rebuilding with, Perl 5.005_56.
 >Date: Tue, 18 May 1999 18:48:32 -0700 (PDT)
 >From: Doug MacEachern <dougm@cp.net>
 >To: Peter Kaas <Peter.Kaas@lunatech.com>
 >cc: George Planansky <george_planansky@harvard.edu>, modperl@apache.org
 >Subject: Re: help: mod_perl solaris 2.6 dso won't start
 >In-Reply-To: <19990515005232.A27892@sparc.ommm.net>
 >On Sat, 15 May 1999, Peter Kaas wrote:
 >> On Fri, May 14, 1999 at 12:28:30PM -0400, George Planansky wrote:
 >> > 
 >> > In contrast, both my httpd and the downloaded binary start and run
 >> > fine with the php3 libphp3.dso that I compiled from source.  So I must
 >> > be close, yes?  Does this mean it's a mod_perl problem, and not
 >> > apache?  Or maybe the way I built perl5?
 >> > 
 >> Did you compile perl without perl's malloc? Make sure you configure perl 
 >> with -Uusemymalloc. For instance:
 >>    sh Configure -Dprefix=/usr/local/perl -des -Uusemyalloc
 >then you also degrade your server performance.  Perl has its own
 >malloc for a reason(s).  build a Perl with -Uusemymalloc and compare the
 >output strace (or truss) vs. -Dusemymalloc.  chances are, with system
 >malloc, you'll see lots more output, mostly brk()'s, eating your cpu.
 >anyhow, this mod_perl-as-dso-under-solaris-core-dump-with-perls-malloc
 >problem is solved in Perl 5.005_56.
    Date: 14 Jun 1999 00:24:53 -0000
    From: ask@apache.org
    [In order for any reply to be added to the PR database, ]
    [you need to include <apbugs@Apache.Org> 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: on solaris 2.6, apache 1.3.6 dumps core with mod_perl-1.19 DSO
    State-Changed-From-To: open-feedback
    State-Changed-By: ask
    State-Changed-When: Sun Jun 13 17:24:52 PDT 1999
    [This is a standard response.]
    This Apache problem report has not been updated recently.
    Please reply to this message if you have any additional
    information about this issue, or if you have answers to
    any questions that have been posed to you.  If there are
    no outstanding questions, please consider this a request
    to try to reproduce the problem with the latest software
    release, if one has been made since last contact.  If we
    don't hear from you, this report will be closed.
    If you have information to add, BE SURE to reply to this
    message and include the apbugs@Apache.Org address so it
    will be attached to the problem report!

View raw message