[rvm-research] Tracing Segmentation Fault in Jikes

Hi,

I am now tracing a segmentation fault in Jikes. This happens directly after
I invoke Jikes and most likely in the boot process. The signal number 11.
OS seems to send a signal to the C code at ./tools/bootloader/sysSignal.c

Yes, there are modifications to the Jikes source and are mostly the Java
code

*Here is the Summary of what Is Printed*:
JikesRVM: hardwareTrapHandler SignalNO:11  Context:0x58498c8c -
InsPtr:0xf7581d57 instFollowPtr:0xffffffff threadPtr:(nil)
jtocPtr:0x600802e0

*Questions:*


   1. *How do I know which line or function either in C or in Java caused
   this error ?*
   2. *Suppose I explicitly added code to the Jikes to make an array out of
   bound exception ? Like int[]  xs = new int[10];. x[100]++. Since, the Jikes
   itself is not running JVM (It is the JVM itself), the previous code at the
   Jikes core could result in segmentation fault and a trap ?*




-- 
Regards,
Khaled Mahmoud

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Jikesrvm-researchers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jikesrvm-researchers