Date: Mon, 18 Jul 2016 12:09:14 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: maintainer-feedback requested: [Bug 211196] java/openjdk8: thread id missing from jstack output against core files Message-ID: <bug-211196-8522-vz66Btbsec@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211196-8522@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
Ron Roskens <ronald.roskens@gmail.com> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to java@FreeBSD.org: Bug 211196: java/openjdk8: thread id missing from jstack output against core files https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211196 --- Description --- Created attachment 172643 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172643&action=edit patch for hotspot/src/os/bsd/vm/os_bsd.cpp When analyzing a JVM core dump, jstack is unable to display any stacktraces for any threads because it cannot match any thread id's. In the JVM on BSD, a thread is represented by two different thread id values, however, only when defined(__APPLE__) does the second value, unique_thread_id, get set. Its unique_thread_id that jstack uses to match thread ids in a core dump. I've been using the attached two local patches. patch-rjr-os_bsd.cpp sets unique_thread_id to the same value as the thread_id. patch-rjr-BsdThread.java adds the unique_thread_id to BsdThread.toString() output.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211196-8522-vz66Btbsec>