As part of an anaconda install, I'm running jetty, and feeding data into
a postgresql database through jetty using another java program. (Don't
ask why we're doing this. That way lies madness) This command works
fine outside of anaconda, but when I try it as part of the CD
installation using anaconda, Java crashes with sig11 on the same malloc
and memset call each time.
>From my rudimentary C programming, a signal 11 is caused by reading
unassigned RAM, or RAM that's somehow faulty. Given that this problem
seems to only occur in anaconda, what in anaconda could be causing java
to try to access this memory address that causes it to crash?
If it helps, I'm using anaconda-11.2.87
Stack: [0x90538000,0x905b9000], sp=0x905b6d54, free space=507k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code,
C=native code)
C [libc.so.6+0x6e077] memset+0x37
C [libc.so.6+0x6812e] __libc_malloc+0x7e
V [libjvm.so+0x4f7c4a]
V [libjvm.so+0x198705]
V [libjvm.so+0x198c26]
V [libjvm.so+0x344492]
V [libjvm.so+0x255f58]
V [libjvm.so+0x2a29ad]
V [libjvm.so+0x29f830]
V [libjvm.so+0x247149]
V [libjvm.so+0x2a6d1a]
V [libjvm.so+0x2a6726]
V [libjvm.so+0x5b5d7d]
V [libjvm.so+0x4fde19]
C [libpthread.so.0+0x543b]
--
Matt Rose <mrose(a)n-able.com>