During some recent debugging I did I found it useful to dump a thread's registers in this manner. Although in this case I was inlining the code in the part of SA where I wanted to see the registers, having it as a clhsdb command would not only be useful to user, but also useful when debugging SA because it would serve as a code snippet to copy-n-paste where needed.
Proposal for the syntax is the same as for the "thread" command:
threadcontext [-v] { -a | id }
Where -a displays all threads, and "id" is used to display a specific thread. -v just means more verbose output, whereas without it for the most part each register printed will just take up one line. I've implemented this and it was trivial, although I still need to come up with a test case.
- is blocked by
-
JDK-8247514 Improve clhsdb 'findpc' ability to determine what an address points to by improving PointerFinder and PointerLocation classes
-
- Resolved
-
- relates to
-
JDK-8285729 serviceability/sa/ClhsdbThreadContext.java timed out
-
- Open
-
-
JDK-8280601 ClhsdbThreadContext.java test is triggering codecache related asserts
-
- Resolved
-
-
JDK-8280770 serviceability/sa/ClhsdbThreadContext.java sometimes fails with 'Thread "SteadyStateThread"' missing from stdout/stderr
-
- Resolved
-
-
JDK-8292201 serviceability/sa/ClhsdbThreadContext.java fails with "'Thread "Common-Cleaner"' missing from stdout/stderr"
-
- Resolved
-
-
JDK-8294920 Missing SP value in Linux x86_32 thread context
-
- Resolved
-