Stas Bekman wrote:
Richard Clarke wrote:
Stas,
Doesn't seem like an apreq problem. It happens in the modperl function.
Any
chance you can rebuild mod_perl with debug mode enabled
(PERL_DEBUG=1), so
we
can see the arguments and file/linenumbers? See:
I'm using FreeBSD 4.7 Release. perl 5.6.1 Mod_Perl/Apache Latest
libapreq 1.1.
Program received signal SIGBUS, Bus error.
0x80b2953 in ap_unescape_url ()
(gdb) bt
#0 0x80b2953 in ap_unescape_url ()
#1 0x8084094 in XS_Apache_unescape_url ()
#2 0x8102623 in Perl_pp_entersub ()
#3 0x80fcf4e
/linenumbers? See:
http://perl.apache.org/docs/1.0/guide/debug.html#PERL_DEBUG_1_Build_Option
Program received signal SIGBUS, Bus error.
0x80b2953 in ap_unescape_url ()
(gdb) bt
#0 0x80b2953 in ap_unescape_url ()
#1 0x8084094 in XS_Apache_unescape_url ()
#2 0x8102623 in Perl_pp_entersub ()
#3
Stas,
Doesn't seem like an apreq problem. It happens in the modperl function.
Any
chance you can rebuild mod_perl with debug mode enabled (PERL_DEBUG=1), so
we
can see the arguments and file/linenumbers? See:
http://perl.apache.org/docs/1.0/guide/debug.html#PERL_DEBUG_1_Build_Option
Richard Clarke wrote:
Stas,
Doesn't seem like an apreq problem. It happens in the modperl function.
Any
chance you can rebuild mod_perl with debug mode enabled (PERL_DEBUG=1), so
we
can see the arguments and file/linenumbers? See: