Stephen [EMAIL PROTECTED] wrote:
I'm no expert at debugging C, but I dont think that the above looks too
healthy
Well, I think I have it figured out, more or less. The root cause of it
seemed to be a rather, um, interesting bit of code in
HTML::Mason::ApacheHandler which makes use of string
Stephen wrote:
[...]
The intent was to create a handler()
routine suitable for both mod_perl 1 and 2 (prototype of ($$) vs attribute
of : method). However, for some reason or another, handler() was being
called as a regular sub, with one parameter.
I have used the technique documented here:
Stephen wrote:
Stephen [EMAIL PROTECTED] wrote:
I'm no expert at debugging C, but I dont think that the above looks too
healthy
Well, I think I have it figured out, more or less. The root cause of it
seemed to be a rather, um, interesting bit of code in
HTML::Mason::ApacheHandler which
Geoffrey Young wrote:
mp1 supports both $$ and :method, so no need to do something special to
make
it work for both mp1 and mp2.
Aah, I'll pass that onto the Mason folks. Ta.
Preloading the module and using the explicit Module-handler method
syntax
in httpd.conf seems to have fixed it.
Greetings,
I'm not sure if this should be sent here, or to the HTML::Mason list, but as
its a segfault, I've sent it here first. I've just upgraded my
apache/mod_perl installation, and have run into a few problems.
Firstly, all of mod_perl's tests pass (although a few are skipped), and
mod_perl
Stephen wrote:
[...]
The GDB backtrace output (from debugging httpd -X) is as follows:
(gdb) bt
#0 0x808d079 in XS_Apache_dir_config ()
#1 0x810a7f7 in Perl_pp_entersub ()
#2 0x8104b24 in Perl_runops_standard ()
#3 0x80c39fe in Perl_call_sv ()
#4 0x80c3b42 in Perl_eval_sv ()
#5 0x80846ce in
Stas Bekman [EMAIL PROTECTED] wrote:
Wearing my bug-tender cap, but not taking the ownership of this bug, I
should
say that your backtrace could be much more useful if you have had rebuilt
apache/perl/mod_perl with debugging symbols enabled. When you do that the
trace will show the arguments
