ails.
Tested on:
Apache/2.0.55 (prefork) mod_python/3.2.6 Python/2.4.2
Apache/2.0.50 (prefork) mod_python/3.2.6 Python/2.3.4
I've tried to reproduce this test manually:
$ /usr/local/sbin/httpd -k start -f
/home/volodya/mod_python-3.2.6/test/conf/test.conf
$ GET http://localhost:2758/tests.p
as able to
reproduce failure of PythonConnectionHandler test under gdb. So here is
backtrace:
> #0 0x58 in ?? ()
> #1 0x2823e4af in conn_readline (self=0x82e7660, args=0x81c702c) at
> connobject.c:193
> #2 0x2825b8b8 in PyCFunction_Call ()
>from /home/volodya/apache20/mod_python-3.2
On Mon, Jan 30, 2006 at 09:40:39PM -0500, Graham Dumpleton wrote:
> Graham Dumpleton wrote ..
> > Extending the above code as:
> >
> > Py_BEGIN_ALLOW_THREADS;
> > rc = ap_get_brigade(c->input_filters, bb, mode, APR_BLOCK_READ,
> > bufsize);
> > Py_END_ALLOW_THREADS;
> >
> > if (!
On Thu, Feb 02, 2006 at 10:54:27PM -0500, Jim Gallacher wrote:
> Graham Dumpleton wrote:
> >To confirm Jim's arithmetic anyway, I say -1 on 3.2.6 as it stands.
> >
> >As to 3.2.7, I say +1, subject to removal of problematic test case
> >as already raised and with us at least confirming tests run OK
On Sun, Feb 05, 2006 at 09:10:15PM -0500, Jim Gallacher wrote:
> Mod_python 3.2.7 tarball is available for test. Here's hoping this will
> be to final time we need your help testing before the official release.
>
> 3.2.7 adds a fix for the connection read issue that was causing problems
> on Fre
