Clinton Gormley wrote:
Clint,
I changed the header I sent from text/html to text/plain and the
segfaulting no longer occuring.
It's more likely to be the headers your server is receiving (eg cookie?)
than the headers it is sending.
Ok, I built my own apache-2.2.4 + mod_perl 2.0, fir
On 5/25/07, Tyler Bird <[EMAIL PROTECTED]> wrote:
Also when I tried to recompile apache since I
have a redhat rpm install of apache 2.0 and mod_perl when I try and
compile apache it complains about libapr already being there and exits.
Remove any mod_perl, apache, and libapreq RPMs before you b
Clinton Gormley wrote:
Clint,
I changed the header I sent from text/html to text/plain and the
segfaulting no longer occuring.
It's more likely to be the headers your server is receiving (eg cookie?)
than the headers it is sending.
Clint, I removed sending any cookies the following
> Clint,
>
> I changed the header I sent from text/html to text/plain and the
> segfaulting no longer occuring.
It's more likely to be the headers your server is receiving (eg cookie?)
than the headers it is sending.
Clinton Gormley wrote:
Hi Tyler
I know next to nothing about reading backtraces, but it looks to me like
your segfault is occurring while your program is trying to parse the
headers.
Before doing any more, I would compile my own version of Apache2,
mod_perl2 and libapreq2, and see if it still o
Hi Tyler
I know next to nothing about reading backtraces, but it looks to me like
your segfault is occurring while your program is trying to parse the
headers.
Before doing any more, I would compile my own version of Apache2,
mod_perl2 and libapreq2, and see if it still occurs.
With regards your
hey guys I read a little more and was able to generate a backtrace for
my apache children segfaulting here it is below.
Program terminated with signal 11, Segmentation fault.
#0 0x0051389a in apr_palloc () from /usr/lib/libapr-1.so.0
(gdb) bt
#0 0x0051389a in apr_palloc () from /usr/lib/libapr
