Vince Moneymaker wrote:
Okay, all of the tests are being passed. I have added the contents of my
startup.pl file to the modperl_startup.pl file and no segfaults are
occurring including even when I change the Handler.pm file as the tests
are being run on it. I have also added some items to the
Hi,
I've got mod_perl installed on my debian sarge/testing box via:
aptitude install libapache2-mod-perl2
and I know my webserver is mod_perl aware
# head /var/log/apache2/error.log
[Sat Apr 23 06:56:28 2005] [notice] Apache/2.0.53 (Debian GNU/Linux)
mod_perl/1.999.21 Perl/v5.8.4 configured -- res
Michael Schout wrote:
I am wondering what the best way is to read POST data under MP2.
In MP1, I was using $r->content for this. In MP2, $r->content does not
exist, so I used the version from an earlier copy of Apache::compat,
which was using $r->get_client_block() instead.
Now, get_client_block()
Vincent Moneymaker wrote:
OK, so yours crash is in require, Vincent. Any chance you could
prepare a tarball that reproduces the problem, so Philippe can
reproduce it easily?
Please grab the template from geoff's site:
http://people.apache.org/~geoff/Apache-Test-skeleton-mp2.tar.gz
In fact better
works in RC4 + libapreq 2.04
use Apache::Request()
sub handler
{
my $r = shift;
my $apr = Apache::Request->new( $r , DISABLE_UPLOADS=>0,
POST_MAX=>10 );
$stringvalue = $apr->param($stringname);
}
RC5 is slightly different from the namespace stuff, and you need to run
one of the
I am wondering what the best way is to read POST data under MP2.
In MP1, I was using $r->content for this. In MP2, $r->content does not
exist, so I used the version from an earlier copy of Apache::compat,
which was using $r->get_client_block() instead.
Now, get_client_block() is apparently depre
Vincent Moneymaker wrote
Vincent Moneymaker wrote:
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f i
Vincent Moneymaker wrote:
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f in Perl_pp_require () from
Vincent Moneymaker wrote:
Here is the output from the backtrace (hope I did it correctly)
Program received signal SIGSEGV, Segmentation fault.
0xdeb3618f in Perl_gv_efullname3 () from
/opt/prod/apache/modules/mod_perl.so
(gdb) bt
#6 0xdeb9293f in Perl_pp_require () from
/opt/prod/apache/modules
Vincent Moneymaker wrote:
Vincent Moneymaker wrote:
I am running Apache 2.0.52 on a solaris 8 box with
mod_perl-2.0.0-RC5. I previously had problems using Apache::Reload
with mod_perl 1.99_19 version back in December and gave up trying to
find a fix. I thought I would try again with the RC5 v
Philip M. Gollucci wrote:
Stas Bekman wrote:
Philip, we have Bundle::Apache2 which is exactly for that purpose.
Feel free to send a patch to add the missing modules.
Yes, I added IPC::Run3 and uped the CGI version :) things to in a patch.
Yup, thank you :)
Though as it can be seen from your list,
Vincent Moneymaker wrote:
I am running Apache 2.0.52 on a solaris 8 box with mod_perl-2.0.0-RC5. I
previously had problems using Apache::Reload with mod_perl 1.99_19 version
back in December and gave up trying to find a fix. I thought I would try
again with the RC5 version but after having up
12 matches
Mail list logo