Re: [Jamvm-general] Jamvm seg faults on Mips ( Big endian )

[JediKnight <ver...@ya...>]

Hi, 

I built gdb for the target and enabled core dump. 

Now when i load the core dump in gdb and a backtrace i get this output:

******************************************************************
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
Core was generated by `/usr/local/jamvm/bin/jamvm -Xms2m -Xmx4m -jar
/root/core_
bundles/framework.jar'.
Program terminated with signal 11, Segmentation fault.
[New process 1048]
[New process 1042]
[New process 1043]
[New process 1044]
[New process 1045]
[New process 1046]
[New process 1047]
[New process 1049]
[New process 1041]
#0  0x2ab64ae0 in ?? ()
(gdb) bt
#0  0x2ab64ae0 in ?? ()
#1  0x2ab64ae8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
***********************************************************************
I was wondering since this a VM instead and not a normal "C" executable,
there might be low level stack manupulation in the code which confuses gdb. 

My question then is how do you debug VM specifically how do i debug Jam VM ? 

TIA,
/JediKnight





-- 
View this message in context: http://old.nabble.com/Jamvm-seg-faults-on-Mips-%28-Big-endian-%29-tp32089143p32159603.html
Sent from the JamVM mailing list archive at Nabble.com.