b***@freebsd.org
2016-07-18 12:09:14 UTC
Ron Roskens <***@gmail.com> has reassigned Bugzilla Automation
<***@FreeBSD.org>'s request for maintainer-feedback to ***@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.
<***@FreeBSD.org>'s request for maintainer-feedback to ***@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.