5.8.0-RC3 still produces the SEGV with apache 1.3.26, mod_perl 1.27,
Apache::Request 1.0 and MaxRequestPerChild 0.
My recipe to reproduce the SEGV currently is: Set MaxRequestPerChild
to 1 and request a static image.
Unless the problem is fixed before 5.8.0 comes out (i.e.~Thursday), I
fear we
On Sat, 29 Jun 2002 16:48:57 -0700 (PDT), Doug MacEachern [EMAIL PROTECTED]
said:
On Mon, 24 Jun 2002, Andreas J. Koenig wrote:
This stack trace is all I have. I cannot reproduce this SEGV at will,
so it will be difficult to obtain additional information. All I can do
is let the
On Sun, 30 Jun 2002, Andreas J. Koenig wrote:
Program received signal SIGSEGV, Segmentation fault.
0x400d8076 in chunk_free (ar_ptr=0x4016ca40, p=0x82fd0a0) at malloc.c:3097
3097malloc.c: No such file or directory.
(gdb) bt
#0 0x400d8076 in chunk_free (ar_ptr=0x4016ca40, p=0x82fd0a0)
On Sun, 30 Jun 2002 15:30:18 -0700 (PDT), Doug MacEachern [EMAIL PROTECTED]
said:
#0 0x400d8076 in chunk_free (ar_ptr=0x4016ca40, p=0x82fd0a0) at malloc.c:3097
#1 0x400d7f5a in __libc_free (mem=0x82fd0a8) at malloc.c:3023
#2 0x8169142 in Perl_safesysfree (where=0x82fd0a8) at
On Mon, 24 Jun 2002, Andreas J. Koenig wrote:
This stack trace is all I have. I cannot reproduce this SEGV at will,
so it will be difficult to obtain additional information. All I can do
is let the webserver run in -X mode and wait. I have no hints (yet)
what kind of request triggers it.
...
This stack trace is all I have. I cannot reproduce this SEGV at will,
so it will be difficult to obtain additional information. All I can do
is let the webserver run in -X mode and wait. I have no hints (yet)
what kind of request triggers it.
Again, as in my older posted SEGV, the line numbers
