FYI,
Original Message
Subject: Re: Bug#666822: Apache 2.4 upload date scheduled for May 30;
mod_perl needs work
Date: Thu, 23 May 2013 15:22:36 +0100
From: Dominic Hargreaves
To: 666...@bugs.debian.org, debian-p...@lists.debian.org
CC: Arno Töll
[Ccing debian-perl to get a sli
Here's the code I mentioned in my last post. It's included in my distro
NoSQL::PL2SQL
#include "EXTERN.h"
#include "perl.h"
#include "XSUB.h"
#include "ppport.h"
SV* typeis ( SV* what ) ;
SV* typeis ( SV* what )
{
if ( SvIOK( what ) )
return newSVpvs( "integer" ) ;
I also encounter this problem occasionally. So your post is quite
familiar.
If the first thing you do is print the parameters, what's the second
thing? Form posts almost always trigger external processes, databases,
mail servers, etc. The external process is more likely to be causing the
f
Hi,
I've got a mod_perl handler which has been working fine for a long time, but
just recently two people have managed to trigger a seg fault under specific
circumstances.
They are POSTing form data
Only happens over https - doesn't happen via http (ie without SSL)
A certain combination of byte
