Re: [rvm-research] Jikes Runtime Exception

Hi,

On 09.03.2018 19:37, Khaled Z Mahmoud wrote:
> I am speculating that maybe the C Code I am calling is corrupting the memory of the JVM.
> Since these are different languages different memory managers are involved. I am basically just using PAPI Library for performance counter monitoring using Overflow mechanism.

Calling C code should be fine if you're using a standard interface (i.e. Jikes RVM syscalls or JNI). You can get more information about the signal handling (e.g. the signal number for each hardware trap) by passing the flag -X:verboseSignalHandling if you're using a recent version of Jikes RVM.

If you think that there's a memory conflict, you could try changing the heap layout. There was a thread about heap layout in the past few days that has some relevant information. You could check that the library isn't mapped in the space that Jikes RVM uses. If necessary, you can move the boot image segments by editing the appropriate .properties file in build/targets/ .


Kind regards,

Erik Brangs

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