Hi Gerald,
I have finally found the difference between a working conf and a
non-working conf:
I get seg faults with this setup:
.
CoreDumpDirectory /tmp/denman
EMBPERL_OPTIONS 512
EMBPERL_ESCMODE 0
Embperl_Syntax EmbperlBlocks
Embperl_AppName
Hi again,
Looking further into the seg faults on my Virtuozzo virtual server:
Just backtraced a core file to find:
(gdb) bt full
#0 0x002a9a23cd0a in Perl_he_dup ()
from /usr/lib64/perl5/5.8.6/x86_64-linux-thread-multi/CORE/libperl.so
No symbol table info available.
#1 0x002a9a23de8
Hi Gerald,
Still getting these in the apache logs
[Sun Sep 30 16:04:57 2007] [notice] child pid 28490 exit signal Bus error (7)
[Sun Sep 30 16:05:11 2007] [notice] child pid 28532 exit signal Bus error (7)
[Sun Sep 30 16:07:05 2007] [notice] child pid 28606 exit signal
Segmentation fault (11)
Gerald,
Thanks for your recent reply.
I have now successfully installed V2.3.0 with no errors.
Still getting seg faults
Although I am new to backtracing, I have attempted to perform one with
the following results:
(gdb) c
Continuing.
Program received signal SIGBUS, Bus error.
[Switching
Hi,
Can you please retry with the just uploaded Embperl 2.3.0.
If you still get segfaults, please send me a stack backtrace.
Gerald
P.S. Please use the Embperl mailinglist for further questions.
Besuchen Sie unseren Messe
