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

Corruption of exitfns[] table when running JDBC tests in 1.2beta4 H build.

    Details

    • Subcomponent:
    • Resolved In Build:
      1.2fcs
    • CPU:
      sparc
    • OS:
      solaris_2.6
    • Verification:
      Not verified

      Description


      gordon.jackson@east 1998-06-02

      I believe that this is an AWT problem (based only on the stack trace which comes immediately before the core dump :(

      This is occuring in JDK1.2Beta4-H when run on ** Solaris 2.6 ** .
      This DOES NOT OCCUR ON SOLARIS 2.5.1.

      This occurs with the JIT both enabled and disabled.

      Here is the trace:

      SIGSEGV 11* segmentation violation
          si_signo [11]: SIGSEGV 11* segmentation violation
          si_errno [0]: Error 0
          si_code [1]: SEGV_MAPERR [addr: 0xea886b64]

              stackpointer=EF031484

      Full thread dump:
          "Screen Updater" (TID:0xebcae688, sys_thread_t:0x251c30, state:CW) prio=4
              at java.lang.Object.wait(Native Method)
              at java.lang.Object.wait(Object.java:303)
              at sun.awt.ScreenUpdater.nextEntry(ScreenUpdater.java:79)
              at sun.awt.ScreenUpdater.run(ScreenUpdater.java:99)
          "AWT-InputMethodManager" (TID:0xebca9518, sys_thread_t:0x22a6d0, state:CW) prio=5
              at java.lang.Object.wait(Native Method)
              at java.lang.Object.wait(Object.java:303)
              at sun.awt.im.ExecutableInputMethodManager.run(InputMethodManager.java:310)
              at java.lang.Thread.run(Thread.java:472)
          "AWT-Motif" (TID:0xebca65d8, sys_thread_t:0x1c0a90, state:CW) prio=5
              at java.lang.Object.wait(Native Method)
              at sun.awt.motif.MToolkit.run(Native Method)
              at java.lang.Thread.run(Thread.java:472)
          "AWT-Input" (TID:0xebca6600, sys_thread_t:0x1c6cb0, state:R) prio=5
              at sun.awt.motif.InputThread.run(Native Method)
          "AWT-EventQueue-0" (TID:0xebca66a8, sys_thread_t:0x1a0ec0, state:R) prio=6 *current thread*
              at java.lang.Runtime.exitInternal(Native Method)
              at java.lang.Runtime.exit(Runtime.java:76)
              at java.lang.System.exit(System.java:537)
              at QuitBox.clickedYesButton(JDBCTestWin.java:482)
              at QuitBox.handleEvent(JDBCTestWin.java:464)
              at java.awt.Window.postEvent(Window.java:588)
              at java.awt.Component.postEvent(Component.java:2360)
              at java.awt.Component.dispatchEventImpl(Component.java:2150)
              at java.awt.Component.dispatchEvent(Component.java:2054)
              at java.awt.EventQueue.dispatchEvent(EventQueue.java:223)
              at java.awt.EventDispatchThread.run(EventDispatchThread.java:63)
          "Finalizer" (TID:0xebc983a0, sys_thread_t:0x58610, state:CW) prio=8
              at java.lang.Object.wait(Native Method)
              at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:113)
              at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:128)
              at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:128)
          "Reference Handler" (TID:0xebc98430, sys_thread_t:0x61890, state:CW) prio=10
              at java.lang.Object.wait(Native Method)
              at java.lang.Object.wait(Object.java:303)
              at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:209)
          "Signal dispatcher" (TID:0xebc982e8, sys_thread_t:0x36c30, state:CW) prio=10
          "Thread-0" (TID:0xebcaeee0, sys_thread_t:0x29660, state:CW) prio=5
      Monitor Cache Dump:
      Registered Monitor Dump:
          utf8 hash table: <unowned>
          JNI pinning lock: <unowned>
          JNI global reference lock: <unowned>
          BinClass lock: <unowned>
          Class linking lock: <unowned>
          System class loader lock: <unowned>
          Code rewrite lock: <unowned>
          Heap lock: <unowned>
          Dynamic loading lock: <unowned>
          Monitor IO lock: <unowned>
          User signal monitor: <unowned>
              Waiting to be notified:
                  "Signal dispatcher" (0x36c30)
          Child death monitor: <unowned>
          I/O monitor: <unowned>
          Alarm monitor: <unowned>
              Waiting to be notified:
              Internal clock thread (ef7a0dd8)
          Thread queue lock: <unowned>
              Waiting to be notified:
                  "Thread-0" (0x29660)
          Monitor registry: owner "AWT-EventQueue-0" (0x1a0ec0, 1 entry)
      Segmentation Fault(coredump)


      This is easily reproduceable, if you've got a few minutes to setup/run the JDBC test harness.
      Please let me know if I can help in putting together a smaller testcase, or running the test harness.


        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                swhitesunw Seth White (Inactive)
                Reporter:
                duke J. Duke (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: