On Thu, 4 Jan 2024 02:06:28 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
> In threadControl.c, at build time you can decide to keep track of thread > names by compiling with "#define DEBUG_THREADNAME". If this is also a debug > build, some extra debugging functions are included in the build, including > "dumpThread(ThreadNode *node)". These are intended to be called from gdb, or > possibly from somewhere in the debug agent implementation, to aid with > debugging. When dumpThread() prints the thread's name, it just uses the name > that was stored when the thread was created. However, the thread name can > change, so dumpThread() should really fetch the current thread name and print > it. > > I also added some commented out code to print other useful fields of the > ThreadNode, including the ThreadState. These can be enabled by the user as > needed. > > Tested with all of tier1, and also ran tier2 and tier4 svc tests. This pull request has now been integrated. Changeset: 387828a3 Author: Chris Plummer <cjplum...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/387828a3f7e4ec5b26954747e756aac212d579ae Stats: 45 lines in 1 file changed: 43 ins; 0 del; 2 mod 8322980: Debug agent's dumpThread() API should update thread's name before printing it Reviewed-by: kevinw, sspitsyn ------------- PR: https://git.openjdk.org/jdk/pull/17259
