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

os::write_memory_serialize_page need a explicit handler in thread native transition

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 5.0u3
    • Fix Version/s: 6
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b60
    • CPU:
      x86
    • OS:
      windows_xp

      Backports

        Description

        When JVM issues write_memroy_serialize_page, an access violation will be generated then handled by exception filter handler, but if customer has JNI code and use MS C++ like
        try {
          // java method invoke
          // others
        }
        catch(...) {
          // user handling code
        }
        When this fault happens in the try block, it will be caught in user handling block and usually user has no idea what this fault is so the process messed up, terminated. An explicit handling needed in JVM so user code will not catch it.

        See bug 5075546 and 6305157 for details.

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                nigottiorcl Nikolay Igotti (Inactive)
                Reporter:
                minqi Yumin Qi
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: