Dorian Taylor wrote:
On Tue, Nov 23, 2004 at 10:08:49PM +, Dorian Taylor wrote:
But I don't see the problem that you describe.
hm, i guess that makes the problem either a mac thing, an apr thing
or an apache thing.
apparently it's httpd-2.1. damnit. that means now i have to backport
mod_dav_lo
On Tue, Nov 23, 2004 at 10:08:49PM +, Dorian Taylor wrote:
> > But I don't see the problem that you describe.
>
> hm, i guess that makes the problem either a mac thing, an apr thing
> or an apache thing.
apparently it's httpd-2.1. damnit. that means now i have to backport
mod_dav_lock.
oh we
> But I don't see the problem that you describe.
hm, i guess that makes the problem either a mac thing, an apr thing
or an apache thing.
> Though I've httpd-2.0 and apr-0. Does this distro crash for you?
i'm rolling back now. i have httpd-2.1 for mod_dav_lock (i tried
just grabbing that separat
Stas Bekman wrote:
Dorian Taylor wrote:
argh, spacy today.
*here* is the file.
Hmm, I've further extended your distro to include a live A-T setup
(attached). I've added:
% cat t/conf/extra.conf.in
PerlModule +APR::CrashMe
I've also tried:
% rm t/conf/extra.conf.in
% echo "PerlLoadModule APR::Crash
Dorian Taylor wrote:
argh, spacy today.
*here* is the file.
Hmm, I've further extended your distro to include a live A-T setup
(attached). I've added:
% cat t/conf/extra.conf.in
PerlModule +APR::CrashMe
and some things in Makefile.PL.
But I don't see the problem that you describe.
Though I've httpd
argh, spacy today.
*here* is the file.
APR-CrashMe-0.01.tar.gz
Description: application/tar-gz
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
oops, sorry, was in the wrong mutt window.
> >what exactly is required from mod_perl in the preflight config
> >stage? does it basically just `use' every preloaded module in the
> >conf to see if it can?
> I'm not sure what do you ask. I meant apr design problem, not modperl's
> one. mod_perl d
Dorian Taylor wrote:
i suspect though that anything trying to directly call apr_terminate()
from an END block would do the same. the debugger gets all fuzzy
when it gets into there though.
Yeah, sounds like a design problem.
what exactly is required from mod_perl in the preflight config
stage? d
> getting things to work. I first spent hours trying to get the mandrake
> cooker binaries to work, but eventually I've built everything from source.
yeah i went that way installing it all on my mac. i typically find
i end up needing the source for reference if nothing else at one
point or anothe
it's kind of a grey area as to where this problem is living - hence
the double post. taking a mod_perl module that uses SVN::Core (e.g.
SVN::Web), and either preloading it via PerlLoadModule/PerlModule,
or the + notation in PerlResponseHandler will cause apache to
segfault somewhere around modperl_
10 matches
Mail list logo
