Re: compatibility problem

2002-05-23 Thread Jie Gao
On Wed, 22 May 2002, Doug MacEachern wrote: On Thu, 23 May 2002, Jie Gao wrote: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 15349)] 0x4031575d in modperl_mgv_lookup (symbol=0x0) at modperl_mgv.c:134 134 if (!symbol-hash) { (gdb) bt #0

Re: compatibility problem

2002-05-23 Thread Doug MacEachern
On Fri, 24 May 2002, Jie Gao wrote: Segmentation fault happens when accessing /export/softwares/data, a subdirectory which does not have an .htaccess file itself, but a subdirectory of which has an .htaccess file containing: hmm. you might want to try building modperl with MP_DEBUG=1 and

Re: compatibility problem

2002-05-22 Thread Jie Gao
On Mon, 20 May 2002, Doug MacEachern wrote: On Fri, 17 May 2002, Jie Gao wrote: use Apache::Constants qw(:common :response M_GET M_POST AUTH_REQUIRED REDIRECT); the :response group in 1.x consists of names which apache has deprecated in 1.3.x and removed in 2.0, for which there are HTTP_*

Re: compatibility problem

2002-05-22 Thread Doug MacEachern
On Thu, 23 May 2002, Jie Gao wrote: and make test says BAD_GATEWAY is not exported by Apache::Constants. are you actually using that constant? i only was using it as an example. Also perl-status doesn't seem to be functioning: Apache::Status doesn't work with 2.0 yet. I am also

Re: compatibility problem

2002-05-22 Thread Doug MacEachern
On Wed, 22 May 2002, Doug MacEachern wrote: On Thu, 23 May 2002, Jie Gao wrote: and make test says BAD_GATEWAY is not exported by Apache::Constants. are you actually using that constant? i only was using it as an example. if you are, you need to change it to HTTP_BAD_GATEWAY. one

Re: compatibility problem

2002-05-22 Thread Doug MacEachern
On Wed, 22 May 2002, Doug MacEachern wrote: Apache::Status doesn't work with 2.0 yet. actually, it kinda does after added SERVER_VERSION to Apache::compat. Enabled mod_perl Hooks does not work, nor does Compiled Registry Scripts, but everything else seems to.

Re: compatibility problem

2002-05-22 Thread Jie Gao
On Wed, 22 May 2002, Doug MacEachern wrote: On Thu, 23 May 2002, Jie Gao wrote: I am also getting: [Thu May 23 14:11:45 2002] [notice] child pid 32213 exit signal Segmentation fault (11) when running my 1.3 module. I couldn't find any coredump, though. Anyone can help?

Re: compatibility problem

2002-05-22 Thread Doug MacEachern
On Thu, 23 May 2002, Jie Gao wrote: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 15349)] 0x4031575d in modperl_mgv_lookup (symbol=0x0) at modperl_mgv.c:134 134 if (!symbol-hash) { (gdb) bt #0 0x4031575d in modperl_mgv_lookup (symbol=0x0) at

Re: compatibility problem

2002-05-20 Thread Doug MacEachern
On Fri, 17 May 2002, Jie Gao wrote: use Apache::Constants qw(:common :response M_GET M_POST AUTH_REQUIRED REDIRECT); the :response group in 1.x consists of names which apache has deprecated in 1.3.x and removed in 2.0, for which there are HTTP_* names that replace the old names. so for

compatibility problem

2002-05-17 Thread Jie Gao
Hi all, I've been trying to get httpd-2.0.35 + mod_perl-1.99_01 work with backward compatibility. MY startupl.pl: #! /usr/bin/perl use lib '/usr/lib/perl5/site_perl/5.6.1/i386-linux/Apache2'; use strict; use Apache::compat (); use Apache2 (); use My::AuthCookieHandler; 1; and this script

Re: compatibility problem

2002-05-17 Thread Peter Rothermel
You'll find a few other issues with AuthCookie and mod_perl-1.9.9_01 beyond the REDIRECT constant. Here's a quick summary: 1) move all the $r-connection-user() calls to $r-user() calls 2) change all the err_header_out() calls to err_headers_out() calls.