New mod_perl works GREAT!

2005-05-14 Thread Igor Chudov
Once I got past the B/S related to CGI.pm and CGI::Deurl (the latter I replaced with my own module, I gave up on Deurl), everything has been working just GREAT. Specifically, I used Apache::SizeLimit to kill my processes when they grow too big. After installation of new mod_perl, these processes

[QUESTION] Overloading/overriding print() when subclassing Apache

2005-05-14 Thread Arne Skjaerholt
Hello all, I'm currently working on a project where I've decided to subclass Apache, and one of the methods I've decided to overload is the print method (so that my main module decides when data actually gets printed, not user modules). Now, I'd like to also override the built-in perl print (like A

Re: [ANNOUNCE] mod_perl 2.0.0 (preview!)

2005-05-14 Thread Malcolm J Harwood
On Saturday 14 May 2005 12:45 pm, Tom Williams wrote: > I learned with mod_perl-2.0.0-RC6 that previous mod_perl installations were > not compatible, requiring removal of those installations before installing > (including building) mod_perl-2.0.0-RC6. That happened with RC5. > Will there be a

Re: RC6 build problems

2005-05-14 Thread Malcolm J Harwood
On Friday 13 May 2005 11:12 pm, Malcolm J Harwood wrote: > "make test" fails with the following: > > .Syntax error on line 101 > of > /home/mjh/devel/abs/local/apache-mod_perl/src/mod_perl-2.0.0-RC6/t/conf/htt >pd.conf: Invalid command 'TypesConfig', perhaps mis-spelled or defined by a > module no

Re: [ANNOUNCE] mod_perl 2.0.0 (preview!)

2005-05-14 Thread Tom Williams
Philippe M. Chiasson wrote: #* Allright folks, RC6 was released a while ago, and various issues were resolved. According to our planned schedule, I am releasing a mod_perl-2.0.0 preview! As before, this is your last chance to affect the new API, since after 2.0.0 is released, incompatible API chang

Re: mod_perl causing seg faults in apache2?

2005-05-14 Thread Grant
> >>>I tracked down an unofficial mod_perl-2.0.0rc5 ebuild and followed > >>>this stuff to the letter: > >>> > >>>http://perl.apache.org/docs/2.0/rename.html > >>> > >>>but got nothing but 500s. You're right it doesn't make sense to track > >>>down segfaults for old software, but upgrading right n

Re: [PMX:####] Re: [MP2] 1.999024 fails on OS X

2005-05-14 Thread Christian Hansen
Philippe M. Chiasson wrote: Just rebuilt myself a fresh blead-perl, fresh httpd-2.0-svn and mod_perl-2.0-svn. All tests passed! My hunch is that's it's something about Apple's Perl, and I'll investigate more later on. For now, I guess the best advice is to try with a self-built Perl and see if that

[ANNOUNCE] mod_perl 2.0.0 (preview!)

2005-05-14 Thread Philippe M. Chiasson
#* Allright folks, RC6 was released a while ago, and various issues were resolved. According to our planned schedule, I am releasing a mod_perl-2.0.0 preview! As before, this is your last chance to affect the new API, since after 2.0.0 is released, incompatible API changes will not happen. So, one

Re: [MP2] 1.999024 fails on OS X

2005-05-14 Thread Christian Hansen
Stas Bekman wrote: Christian, any difference if you test with perl w/o ithreads? Yes, perl 5.8.6 compiled without ithreads works. perl 5.8.5 and 5.8.6 with ithreads fails. Regards Christian Hansen

[PMX:####] Re: [MP2] 1.999024 fails on OS X

2005-05-14 Thread Philippe M. Chiasson
Philippe M. Chiasson wrote: Philippe M. Chiasson wrote: > Stas Bekman wrote: > >>Christian Hansen wrote: >> >> >>>Program received signal EXC_BAD_ACCESS, Could not access memory. >>>0x014563fc in S_mess_alloc () >>> >>>(gdb) bt >>>#0 0x014563fc in S_mess_alloc () >>>#1 0x014566e8 in Perl_vmess (

Re: [MP2] 1.999024 fails on OS X

2005-05-14 Thread Philippe M. Chiasson
Stas Bekman wrote: > Christian Hansen wrote: > >> Program received signal EXC_BAD_ACCESS, Could not access memory. >> 0x014563fc in S_mess_alloc () >> >> (gdb) bt >> #0 0x014563fc in S_mess_alloc () >> #1 0x014566e8 in Perl_vmess () >> #2 0x014571dc in Perl_vcroak () >> #3 0x014576b8 in Perl_c