Chad Arimura wrote:
Sorry.. 2 hours of messing around, I decide to email the list, and 3 minutes
later I figure out the problem.
PerlHandler Apache::PerlRun
The answer is wrong. It still runs under mod_perl, but in "mod_cgi"-like mode,
not "mod_cgi". See my other reply.
--
_
Chad Arimura wrote:
I setup our server to handle requests through mod_perl with the following
directive:
Options FollowSymLinks ExecCGI
Order allow,deny
Allow from all
SetHandler perl-script
PerlHandler Apache::Registry
There is a subdirectory underneath there that I do NOT
Sorry…. 2 hours of messing around, I
decide to email the list, and 3 minutes later I figure out the problem.
PerlHandler Apache::PerlRun
If anybody has anything to add, please
do. But it works now.
Cheers,
Chad
From: Chad Arimura
[mailto:[EMAIL PROTECTED]
Se
I setup our server to handle requests through mod_perl with
the following directive:
Options FollowSymLinks ExecCGI
Order allow,deny
Allow from all
SetHandler
perl-script
PerlHandler Apache::Registry
There is a subdirectory underneath there that I do NOT wan
[Chris, please keep the thread on the list. Thanks]
Christopher P. Lindsey wrote:
[Thu May 20 03:19:31 2004] [notice] child pid 10522 exit signal
Segmentation fault (11)
You need to show us the core backtrace. And may be rebuild your mod_perl
and/or perl with debug enabled before that. You also
Christopher P. Lindsey wrote:
I'm having a weird problem with certain modules causing perl scripts to
segfault. The errors in the log are like
[Thu May 20 03:19:31 2004] [notice] child pid 10522 exit signal Segmentation fault (11)
You need to show us the core backtrace. And may be rebuild you
BINGO!
If you're ever in San Diego, please contact me. I owe you a beer and dinner.
Dave
At 12:49 AM 5/20/2004, Perrin Harkins wrote:
Dave Boodman wrote:
I don't remember you mentioning that before. If something is not
getting committed to the database, that would cause the process that did
the in
I'm having a weird problem with certain modules causing perl scripts to
segfault. The errors in the log are like
[Thu May 20 03:19:31 2004] [notice] child pid 10522 exit signal Segmentation fault
(11)
The module causing the problems is Sys::Hostname.
The perl script has the line
use Sy
On Thu, 20 May 2004, Steve Hay wrote:
> Randy Kobes wrote:
>
> >On Thu, 20 May 2004, Geoffrey Young wrote:
> >
> >>a release candidate for mod_perl 1.99_14 is now available for testing.
> >>
> >>
> >Hi Geoff,
> > On Win32 (perl-5.8.3, ActivePerl 809 compatible), with
> >Apache/2.0.49, there's a
> I suppose it's coming from perl_shutdown below:
>
> static void mp_dso_unload(void *data)
> {
> array_header *librefs;
>
> librefs = xs_dl_librefs((pool *)data);
> perl_destruct_level = 2;
> perl_shutdown(NULL, NULL);
> unload_xs_so(librefs);
> }
mod_perl as a dso in 1.0 i
Steve Hay wrote:
>Your patch seems fine anyway, apart from one problem: I have
>apache\conftree.t failing tests 6-7. Here's the output under -verbose:
>
># expected: C:\apache2\sources\mod_perl-1.99_14-dev\t\htdocs
># received: "C:\apache2\sources\mod_perl-1.99_14-dev\t\htdocs"
>not ok 6
># expe
Randy Kobes wrote:
>On Thu, 20 May 2004, Geoffrey Young wrote:
>
>
>
>>a release candidate for mod_perl 1.99_14 is now available for testing.
>>
>>
>Hi Geoff,
> On Win32 (perl-5.8.3, ActivePerl 809 compatible), with
>Apache/2.0.49, there's a problem (often) in starting the
>tests, due to T
And that is the correct primary key for this table?
yes
> The return from the
->search looks like
>
> $VAR1 = \bless( {
>
'sysid' => '158'
>
}, 'Lib::Systems' );
> $VAR1 = \bless( {
>
'sysid' => '1065'
>
}, 'Lib:
PK wasn't the problem. If you don't define it, it uses the first col. Even
explicitly defined it didn't work.
The return from the ->search looks like
$VAR1 = \bless( {
'sysid' => '158'
}, 'Lib::Systems' );
$VAR1 = \bless( {
'sysid' => '10
[EMAIL PROTECTED] wrote:
Hi Stas
Sorry, are you saying that you feel the problem is in the Perl code rather
than mod_perl ? I managed to track the fact that the Perl_safesysfree() is
a Perl method, but could not determine if that was the cause or another
symptym of the error we are seeing.
Frankly,
Hi Stas
Sorry, are you saying that you feel the problem is in the Perl code rather than
mod_perl ?
I managed to track the fact that the Perl_safesysfree() is a Perl method, but could
not determine if that was the cause or another symptym of the error we are seeing.
Below are some additional sec
Dave Boodman wrote:
I don't remember you mentioning that before. If something is not
getting committed to the database, that would cause the process that did
the insert to see it, and none of the others. You also should not be
able to see it when connecting to the database from a query tool if it
17 matches
Mail list logo
