> I can't expect that you'll still remember this thread.
I still do remember the problem and I had given it some thoughts since our
last email, but didn't got an idea for a solution.
>
> I just wanted to follow up with you so you could confirm or deny the
> question of Embperl 2.x, Apache 1.x a
I can't expect that you'll still remember this thread. However, I
think I may have stumbled on to the solution. To recap, whenever I'd
try Embperl 2.x I would be able to segfault httpd threads. If I ran
'httpd -X' I could crash the web server with just a few refreshes of an
epl page. Howeve
>
> Is there a configuration option or maybe a special variable that would
> allow me to turn off dynamic table handling? Maybe that would help me
> determine more consistently if the bug you mentioned is my issue. Or is
> that what "$maxrow" and "$maxcol" are for? Thanks.
>
$maxrow and $maxcol
I have confirmed that 1.3.4 works fine. :-\ I guess I'll have to stick
with that until this is sorted out.
On Fri, Nov 15, 2002 at 07:27:09PM -0500, Saadiq Rodgers-King scribbled:
> I am using the latest 2.0b9-dev3 from CVS and I'm able to segfault
> Apache at will. I start a single process ins
I am using the latest 2.0b9-dev3 from CVS and I'm able to segfault
Apache at will. I start a single process instance of Apache (httpd -X).
If I hit an html file and then follow that request with an epl file,
that's enough for the segfault.
saadiq@moko:~/dev$wget -S -O /dev/null --cache=off --http
On Wed, Nov 13, 2002 at 09:21:23AM +0100, Gerald Richter scribbled:
>
> > Well, you were right. The httpd was crashing.
>
> Not quite, the backtrace shows:
>
> Program received signal SIGPIPE, Broken pipe.
>
> This is not really a crash, but looks like a timeout (the client stops
> waiting for
> Well, you were right. The httpd was crashing.
Not quite, the backtrace shows:
Program received signal SIGPIPE, Broken pipe.
This is not really a crash, but looks like a timeout (the client stops
waiting for the repsonse)
Is it possible that the output takes a long time or gets huge?
I rec
>
> saadiq@moko:~$ wget -S -O /dev/null --http-user=blah --http-passwd=blah
http://www.blah.com/bronze.epl
> --20:03:31-- http://www.blah.com/bronze.epl
>=> `/dev/null'
> Resolving www.blah.com... done.
> Connecting to www.blah.com[IP snipped]:80... connected.
> HTTP request sent, awai
