You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Geek Boy <ge...@hotmail.com> on 2000/07/27 01:41:54 UTC

Win32: mod_perl and ActiveState queries...

I've compiled: Apache/1.3.12 (Win32) mod_perl/1.24 in conjunction with 
ActiveState's perl ver 5.6.0 (build 616) under NT... Unfortunately this does 
not work. The mod_perl instructions are fairly easy to follow needed only 
minor changes for my situation. The docs did mention that ActiveState's perl 
is not supported, but with the latest builds it now compiles nicely. (No 
more PERL_OBJECT). As soon as I tried to run the mod_perl tests I saw Apache 
start with:

Apache/1.3.12 (Win32) mod_perl/1.24 Perl/v5.6.0 running...

followed by the immediate "Application Error" death of Apache - core dump.

1) In all my futile attempts at starting Apache I've not seen the 
"Perl/v5.6.0" part of the startup message before, I'm wondering where this 
is coming from. (Something in the httpd.conf file I'd assume, but nothing 
looked relevant?)

2) In my very futile attempts I've got Apache up without an immediate core 
dump. When Apache is asked for a URL that corresponds to a static HTML page 
it will work. When a request is for a CGI, a script to be passed to 
mod_perl, or even a directory that needs an index page created, Apache 
immediately gives an "Application Error" and dumps and even static HTML 
requests will not work after this.

3) I couldn't find any mention of a built-in log generating httpd.conf 
command for mod_perl in all the docs. Might this be an easy thing to add for 
debugging? (I'm thinking like TransferLog, ScriptLog, or SSLLog/SSLLogLevel 
of mod_ssl)
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com


Re: Win32: mod_perl and ActiveState queries...

Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Wed, 26 Jul 2000, Geek Boy wrote:

> I've compiled: Apache/1.3.12 (Win32) mod_perl/1.24 in conjunction with 
> ActiveState's perl ver 5.6.0 (build 616) under NT... Unfortunately this does 
> not work. The mod_perl instructions are fairly easy to follow needed only 
> minor changes for my situation. The docs did mention that ActiveState's perl 
> is not supported, but with the latest builds it now compiles nicely. (No 
> more PERL_OBJECT). As soon as I tried to run the mod_perl tests I saw Apache 
> start with:
> 
> Apache/1.3.12 (Win32) mod_perl/1.24 Perl/v5.6.0 running...
> 
> followed by the immediate "Application Error" death of Apache - core dump.
[...] 
> 2) In my very futile attempts I've got Apache up without an immediate core 
> dump. When Apache is asked for a URL that corresponds to a static HTML page 
> it will work. When a request is for a CGI, a script to be passed to 
> mod_perl, or even a directory that needs an index page created, Apache 
> immediately gives an "Application Error" and dumps and even static HTML 
> requests will not work after this.

I found this as well with ActiveState's build - certainly
there's progress with respect to not having PERL_OBJECT
to deal with, as now mod_perl does compile under ActiveState's
build of perl 5.6.0 (although I think Jochen Wiedmann also managed 
to compile mod_perl with ActiveState's build of perl 5.005_03, but
didn't get it to run). However, it does just exit immediately
with a fatal error - this probably has something to do with
the compile-time flags that ActiveState sets to enable fork
emulation, as a Win32 perl compiled without these flags leads to
a working mod_perl.

best regards,
randy kobes


Re: Win32: mod_perl and ActiveState queries...

Posted by Matt Sergeant <ma...@sergeant.org>.
On Wed, 26 Jul 2000, Geek Boy wrote:

> I've compiled: Apache/1.3.12 (Win32) mod_perl/1.24 in conjunction with 
> ActiveState's perl ver 5.6.0 (build 616) under NT... Unfortunately this does 
> not work. The mod_perl instructions are fairly easy to follow needed only 
> minor changes for my situation. The docs did mention that ActiveState's perl 
> is not supported, but with the latest builds it now compiles nicely. (No 
> more PERL_OBJECT). As soon as I tried to run the mod_perl tests I saw Apache 
> start with:
> 
> Apache/1.3.12 (Win32) mod_perl/1.24 Perl/v5.6.0 running...
> 
> followed by the immediate "Application Error" death of Apache - core dump.
> 
> 1) In all my futile attempts at starting Apache I've not seen the 
> "Perl/v5.6.0" part of the startup message before, I'm wondering where this 
> is coming from. (Something in the httpd.conf file I'd assume, but nothing 
> looked relevant?)

You've gotten far further than most people ever got with their 5xx series,
so I suggest some judicious use of the debugger (the Vis studio one) to
find out where it bombs out. More to the point - if you compiled with
debugging, VS should pop up with a stack trace immediately upon
segfault (even if you're not running it).

-- 
<Matt/>

Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org