On 13-Apr-2000 Gerald Richter wrote:
Trying to use Apache::Session with Embperl 1.2.1, mod_perl 1.21,
Apache 1.3.9.
I've got this running on another machine just fine with the exact
same setup (I
think).
When I try access an Embperl page that uses %udat I get:
[Thu Apr 13 14:51:05 2000]
On 13-Apr-2000 Mark Ng wrote:
can you tell me the following about your 2 systems (the one that works and
the new
one), I have the same problem.
I need to know:
Versions of: Perl
Both are 5.004_04
apache
Both are 1.3.9
modperl
Both are 1.21
embperl
Both are 1.2.1
OS (Exact
Trying to use Apache::Session with Embperl 1.2.1, mod_perl 1.21,
Apache 1.3.9.
I've got this running on another machine just fine with the exact
same setup (I
think).
When I try access an Embperl page that uses %udat I get:
[Thu Apr 13 14:51:05 2000] [notice] Apache/1.3.9 (Unix)
If you tell me what to do I'll try to get a stack backtrace.
http://perl.apache.org/embperl/Faq.pod.1.html#make_test_fails_with_a_SIG
_
Gerald
#0 0xff1d7540 in Perl_sv_clear ()
from
/opt/gnu/depot/perl5.004_04/lib/sun4-solaris/5.00404/CORE/libperl.so
It crashs somewhere deep inside of Perl, so it's hard to say what's happeing
here.
I would first try to recompile all modules (maybe Perl itself also), to make
sure things fit
On Thu, 13 Apr 2000, Jason Bodnar wrote:
Hmmm ... maybe it's a problem with Solaris 5.7?
Can you try the binaries from the 2.6 box on the 2.7 box to see if that
works? That would at least kind of indicate whether it's an OS bug or a
configuration bug.
-Mark
The binaries on both boxes are the same. They get rdist'd out from one
machine every night.
I'm going to rebuild the latest versions of everything on the 2.7 machine
tomorrow and see if that makes a difference.
At 10:57 PM 4/13/00 -0400, Mark Imbriaco wrote:
On Thu, 13 Apr 2000, Jason Bodnar
this copy-n-paste from ~/Mail/.sent-mail-dec-1999 might help:
---
a few things could shed some more light:
build a libperld.a and compile with PERL_DEBUG=1 (see SUPPORT doc)
and/or, in gdb:
(gdb) source mod_perl-1.21/.gdbinit
(gdb) curinfo
should tell you the line/filename of the offending
