Segfault during jvm initialization
Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=2441
Reported by Martin Stjernholm mast@roxen.com
Get this when I try to start a Roxen:
: Executing /export/mast/2.2/server/bin/roxen -DDEBUG
-DMODULE_DEBUG -DENABLE_THREADS -DRAM_CACHE -DENABLE_THREADS "-M/export/mast/2.2/server/etc/modules" "-I/export/mast/2.2/server/etc/include" "-I/export/mast/2.2/server/base_server" "-P/export/mast/2.2/server" -w base_server/roxenloader.pike --remove-dumped 16:24:09 : ---------------------------------------------------------- 0m 0.0s : Pike v7.2 release 226, Roxen WebServer 2.2.230 : Starting mysql ... : "bin/roxen_mysql" "--defaults-file=/export/mast/2.2/configurations/_mysql/my.cfg" "--socket=/export/mast/2.2/configurations/_mysql/socket" "--skip-networking" "--skip-locking" "--basedir=/export/mast/2.2/server/mysql/" "--datadir=/export/mast/2.2/configurations/_mysql" "--pid-file=/export/mast/2.2/configurations/_mysql/mysql_pid" "--user=root" : Done 3.23.31 [331.5ms] : Loading pike modules ... 16:24:14 : 0m 4.9s : mysql: bin/roxen_mysql: ready for connections : Done [6390.4ms] : Loading roxen ... Segmentation Fault - core dumped
(gdb) bt
#0 0xdeb0c192 in InitializeExecEnv () from
/i/jdk/1.2.2_006/jre/lib/i386/classic/libjvm.so
#1 0xdeb30e79 in InitializeJavaVM () from
/i/jdk/1.2.2_006/jre/lib/i386/classic/libjvm.so
#2 0xdeb16488 in JNI_CreateJavaVM () from
/i/jdk/1.2.2_006/jre/lib/i386/classic/libjvm.so
#3 0xdeb9ce0b in f_create (args=0) at
/home/mast/Pike/7.2/src/modules/Java/jvm.c:2846
#4 0x8084a1c in mega_apply (type=APPLY_LOW, args=0, arg1=0x86432c4,
arg2=0x0)
at /home/mast/Pike/7.2/src/interpret.c:1228
#5 0x80861c3 in apply_lfun (o=0x86432c4, fun=1, args=0) at
/home/mast/Pike/7.2/src/interpret.c:1624
#6 0x80e3d2b in call_pike_initializers (o=0x86432c4, args=0) at
/home/mast/Pike/7.2/src/object.c:255
#7 0x80e4152 in parent_clone_object (p=0x8565c60, parent=0x8643304,
parent_identifier=0, args=0)
at /home/mast/Pike/7.2/src/object.c:317
#8 0x8084a63 in mega_apply (type=APPLY_STACK, args=0, arg1=0x0, arg2=0x0)
at /home/mast/Pike/7.2/src/interpret.c:1240
#9 0x80833ba in eval_instruction_without_debug (pc=0x8520918
"hD\001v\023")
at /home/mast/Pike/7.2/src/interpret_functions.h:1489
#10 0x8084dc1 in mega_apply (type=APPLY_LOW, args=0, arg1=0x8643304,
arg2=0xe)
at /home/mast/Pike/7.2/src/interpret.c:799
#11 0x80861c3 in apply_lfun (o=0x8643304, fun=1, args=0) at
/home/mast/Pike/7.2/src/interpret.c:1624
#12 0x80e3d2b in call_pike_initializers (o=0x8643304, args=0) at
/home/mast/Pike/7.2/src/object.c:255
#13 0x80e3ee2 in debug_clone_object (p=0x83fa908, args=0) at
/home/mast/Pike/7.2/src/object.c:280
#14 0x80844e2 in mega_apply (type=APPLY_STACK, args=0, arg1=0x0, arg2=0x0)
at /home/mast/Pike/7.2/src/interpret.c:1051
#15 0x80833ba in eval_instruction_without_debug (pc=0x834b834
"ei\004&\004\003\002G")
at /home/mast/Pike/7.2/src/interpret_functions.h:1489
#16 0x8084dc1 in mega_apply (type=APPLY_LOW, args=3, arg1=0x82f401c,
arg2=0x28)
at /home/mast/Pike/7.2/src/interpret.c:799
/.../
It might be some clue that the server tree has been copied to another location from where it used to run.