0 Replies Latest reply on Nov 1, 2011 7:20 PM by 894863

    Discrepancy between gamma and java executables

      Im trying to debug an issue with our JVM that is running classes created for 1.7. I downloaded the source, built it, and when I used the generated java executable, everything worked fine. When I went to debug, I saw a hotspot scriptfile in the build/linux-amd64/hotspot/outputdir/linux_amd64_compiler2/debug directory that calls an executable called gamma (and will even launch gdb if I pass that as a parameter). The issue is that the hotspot/gamma executable is running:

      Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
      OpenJDK 64-Bit Server VM (build 21.0-b17-debug, mixed mode)

      (according to ./hotspot -version)

      Even though the generated production j2re-image executable is

      OpenJDK Runtime Environment (build 1.7.0-internal-stermanj_2011_10_06_10_49-b00)
      OpenJDK 64-Bit Server VM (build 21.0-b17, mixed mode)

      This makes sense as when I try to run our production test with the gamma executable, I crash with an error saying that a classfile version is too new for the jvm.

      Is there anyway that I can build a debugable gamma executable for java version 1.7 so that I can easily start debugging my issue on our production machines?

      Edited by: 891860 on 01-Nov-2011 11:40

      Edited by: 891860 on 01-Nov-2011 12:19