Ged Haywood wrote:
Hello there,
On Fri, 18 Oct 2002 [EMAIL PROTECTED] wrote:
Hardware is definitely not at fault.
[snip]
[snip]
[snip]
first backtrace shows the segfault happening in mod_perl_sent_header(),
and the second shows it happening in the ap_make_array() which was from
Daniel,
Could be bad hardware. Search google for Signal 11.
Probably your memory (usual cause I've seen).
good luck.
Ed
On Tue, Oct 08, 2002 at 09:46:16AM -0700, [EMAIL PROTECTED] wrote:
Sorry for the repost, but no responses so far, and I need some help with
this one.
I've managed to
Thanks for the reply Ed. Hardware is definitely not at fault. Our site
proxies requests off to several backend servers and they all segfault in
the same way. I believe that there's a problem with libapreq or with
mod_perl itself. Unfortunately I'm not skilled enough in C programming
(yet) to
I experienced the same segfaults after building/installing mod_perl
1.27, apache_1.3.27.
At first I built mod_perl inside the apache tree (USE_DSO=1), this
resulted in 'make test' without any errors, but segfaults as soon as i
tried to contact the apache server if got errors (Segmentation
Hello there,
On Fri, 18 Oct 2002 [EMAIL PROTECTED] wrote:
Hardware is definitely not at fault.
[snip]
Some info:
/usr/apache-perl/bin/httpd -l
Compiled-in modules:
http_core.c
mod_env.c
mod_log_config.c
mod_mime.c
mod_negotiation.c
mod_status.c
mod_include.c
Ed wrote:
Could be bad hardware. Search google for Signal 11.
That's actually pretty rare. Segfaults are usually just a result of
memory-handling bugs in C programs.
- Perrin
On Fri, Oct 18, 2002 at 03:54:22PM -0400, Perrin Harkins wrote:
Ed wrote:
Could be bad hardware. Search google for Signal 11.
That's actually pretty rare. Segfaults are usually just a result of
memory-handling bugs in C programs.
I saw the problem when someone had their memory speed too
Sorry for the repost, but no responses so far, and I need some help with
this one.
I've managed to get a couple of backtraces on a segfault problem we've
been having for months now. The segfaults occur pretty rarely on the
whole, but once a client triggers one on a particular page, they do not
