clumatra: recent ?regression?

[Jules Gosnell]

Guys,

thought that I should let you know.

my overnight builds 15/16th may for both hardware and simulated 
jdk-1.8/graal/okra sumatra stacks both suffered from crashed vms and 
have continued to do so, until I tracked down the test in question and 
disabled it.

here are the full logs:

http://ouroboros.dyndns-free.com/ci/view/clumatra/job/clumatra-hardware-acceleration/246/consoleText
http://ouroboros.dyndns-free.com/ci/view/clumatra/job/clumatra-simulated-acceleration/199/consoleText

if you scroll right to the bottom of each you will find that they end 
prematurely without a test summary - one silently, the other reports a segv:

|7  |8  |9     |10
    locals:  |- 
         |- 
     |-  |-  |-  |-  |-  |-  |-  |d9|j  |-
    stack: 
|vobject:Ratio:1{numerator=Object[null],denominator=Object[null]} 
|vobject:Ratio:1{numerator=Object[null],denominator=Object[null]}  |   | 
   |   |   |   |   |   |      |
at clojure.lang.Numbers.divide(Numbers.java:157) [bci: 46]
             |0  |1  |2
    locals:  |-  |-  |-
at clojure.lang.Numbers.divide(Numbers.java:3731) [bci: 8]
             |0  |1  |2  |3
    locals:  |-  |-  |-  |-
at clumatra.numbers_test$fn$reify__7461.invoke(numbers_test.clj:54) 
[bci: 35]
             |0     |1     |2  |3  |4
    locals:  |-     |-     |-  |-  |-
    stack:   |d3|a  |s0|i  |   |   |

 > 	ld_kernarg_u64 $d16, [%_deoptInfo];
 > 	                     ^
input(63,23): Symbol not found
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fcbe29ab08d, pid=24144, tid=140515433301760
#
# JRE version: OpenJDK Runtime Environment (8.0) (build 
1.8.0-internal-jenkins_2014_05_16_09_06-b00)
# Java VM: OpenJDK 64-Bit Server VM (25.0-b63-internal-graal-0.3 mixed 
mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libokra_x86_64.so+0x59508d] 
Java_com_amd_okra_OkraKernel_setLaunchAttributes+0x43

I can reproduce the problem with any required flags, and provide 
relevant src code (java) if someone is interested in looking at this. 
For now, I will just lose the problematic test.

perhaps something has changed and I need to update my build ?

thanks for all your hard work on graal,


Jules