On Thu, 3 Feb 2005, Stas Bekman wrote:
where is the modperl confguration? As far as you've shown there is no mod_perl involved in serving any requests. (Hint: show us Directory/Location/etc container responsible for a request that has triggered the segfault)
<Directory "/home/nk/www/vhosts/web/apps/">
SetHandler perl-script
PerlResponseHandler ModPerl::Registry
PerlOptions +ParseHeaders +GlobalRequest
Options ExecCGI
</Directory>============================================
I have changed the startup.pl file to read to remove as many variables as possible. It still segfaults with this minimal configuration
#!/usr/bin/perl
1;
============================================
Please reread my original reply. I still have no idea how you've invoked the script. i.e. show us the URL that you've called. and above I've asked you for the relevant config section.
I invoke the script by running http://localhost:8080/apps/test
Resulting in a closed connection and
[Thu Feb 03 21:25:19 2005] [notice] child pid 7393 exit signal Segmentation fault (11)
========================
Is a script using threads beneath the mod_perl interpretor expected to work or is this a dark corner of mod_perl best left untouched?
#!/usr/bin/perl use strict; require threads;
my $thread = threads->create(sub { print "I am a thread"},undef);Thank you for your time.
