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

jdk crash C [libsystem_c.dylib+0xa24f0] strlen+0x10

XMLWordPrintable

    • x86
    • os_x

      (Non reproducible) crash during running NetBeans with -J-Xdebug -J-Xnoagent -J-Xrunjdwp:transport=dt_socket,suspend=n,server=y,address=8765 args.
      Tried to connect debugger but did not suceed, JVM crashed. Attaching log. Please reassign properly.

      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      # SIGSEGV (0xb) at pc=0x00007fff899014f0, pid=28896, tid=5925048320
      #
      # JRE version: 7.0_04-b21
      # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.0-b21 mixed mode bsd-amd64 compressed oops)
      # Problematic frame:
      # C [libsystem_c.dylib+0xa24f0] strlen+0x10
      #
      # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
      #
      # An error report file with more information is saved as:
      # /Users/tomas/space/core-main/hs_err_pid28896.log
      #
      # If you would like to submit a bug report, please visit:
      # http://bugreport.sun.com/bugreport/crash.jsp
      # The crash happened outside the Java Virtual Machine in native code.
      # See problematic frame for where to report the bug.
      #
      Moving to serviceability, since the stack trace has libjdwp.dylib
      calling strlen, which then gets a SEGV.
      Looked through the jdwp part of the stacktrace, don't see anything suspicious going on here.
      If we won't get a repro, I don't really see how we can continue working effectively with this bug.

            Unassigned Unassigned
            tmusil Tomáš Danek (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: