Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4255089

Invalid Page Fault in Zelix KlassMaster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P1 P1
    • 1.0.1
    • 1.0
    • hotspot
    • 1.0.1
    • x86
    • windows_98



      Name: mc57594 Date: 07/18/99


      Can consistently get the following page fault when running Zelix KlassMaster 2.1.1h in Windows 98 and Windows NT 4. The problem doesn't occur if the -Xint option is used.

      JAVA caused an invalid page fault in
      module JVM.DLL at 0177:080b36a3.
      Registers:
      EAX=00000002 CS=0177 EIP=080b36a3 EFLGS=00010202
      EBX=035220d4 SS=017f ESP=02d6f78c EBP=03522174
      ECX=035220d4 DS=017f ESI=00000000 FS=1137
      EDX=0812cc38 ES=017f EDI=00000001 GS=0000
      Bytes at CS:EIP:
      8b 08 eb 02 33 c9 8b 11 ff 52 40 85 c0 0f 85 d1
      Stack dump:
      00000001 00000000 03522174 03409c58 685f64ea 3fee6664 080da86a 000000cf 000000ce 02d6f85c 02d6fa0c 03522174 02d6f85c 02d6fa0c 0806e749 00000000

      To reproduce:
      1) Obtain the evaluation copy of Zelix KlassMaster (ZKMEval.zip)
         from http://www.zelix.com/klassmaster/download.html.
         Expand the the file into some directory.
         Alternatively, I will email the file on request.
      2) Start Zelix KlassMaster with a command such as
         java -mx64m -classpath ZKM.jar;C:\jdk1.2\jre\lib\rt.jar ZKM
      3) Click on the "I Agree" Button
      4) Select ZKM.jar then press the ">" button then press the "OK"
         button
      5) When it is displayed, press "OK" on the "Class Load Warnings"
         Dialog.
      6) Select the Tools/Obfuscate menu option
      7) Click on the "Next" button on the
         "Obfuscate Name Exclusion Options" dialog
      8) Click "OK" on the "Obfuscate Options" dialog
      9) After about 30secs you will get the Invalid Page Fault

      ===================================================
      Hi Mark,

      Sorry for the vagueness. This problem occurs only with the latest HotSpot
      as per below:
      java -version
      java version "1.2.2"
      HotSpot VM (1.0.1, mixed mode, build c)

      The problem goes away if I use the -Xint flag or if I change the name of the
      hotspot directory so that the 1.2.2 classic VM is used as per below:
      java -version
      java version "1.2.2"
      Classic VM (build JDK-1.2.2-U, native threads, symcjit)

      Please let me know if I can be of any further assistance.

      Svet Kovich

      (Review ID: 85608)
      ======================================================================

            mpalecznsunw Michael Paleczny (Inactive)
            mchamnessunw Mark Chamness (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: