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
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
Whoa guys, we do actually have somewhat of a clue over here. That piece
was a mistake (for the same reasons all of you took issue with) and was
pulled as soon as I explained the problems with it (and before I'd ever
seen any of the comments on list).
The url to the story, and most of our site,
Perrin Harkins wrote:
[EMAIL PROTECTED] wrote:
This is a bug introduced by having to insert workarounds for segfaults
caused by Apache::Cooke/mod_perl. I've been asking for help with this
issue for off and on for months now.
I suggest you stop using Apache::Cookie and see if the segfaults
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
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
stop. The length and content of the request are key in making the
segfaults
Hey list,
To be able to pass some notes across php subrequest calls which in turn
call a mod_perl handlers we've overriden Apache::SubRequest::run() in
startup.pl like so:
### save the original method
*NFN::run_save = \Apache::SubRequest::run;
## build our custom version
sub NFN::run_custom
Hi all,
I'm having an odd problem with a particular registry script.
This script causes a segmentation fault at the first usage of
Apache::Util::escape_uri(),
This same script also uses Apache::Util::escape_html() with no problems
at all.
Other scripts on this same server use
darren chamberlain wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] said something to this effect on
12/17/2001:
I'm recording a url at the beginning of an app to restore the
entrance url:
sub set_referer {
my $self = shift;
if ($self-{R}) {
require Apache::Cookie;
darren chamberlain wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] said something to this effect on
12/18/2001:
Use escape_uri and unescape_uri, or some other pair of reversable
functions. For example, store it as:
Tried this and it appears that Apache::Util escapes the same
characters that
Hi all,
I'm recording a url at the beginning of an app to restore the
entrance url:
sub set_referer {
my $self = shift;
if ($self-{R}) {
require Apache::Cookie;
my $cookie = Apache::Cookie-new($self-{R},
-name=
11 matches
Mail list logo
