On 05/06/2024 07:45, Iñigo Mediavilla wrote:
Thanks, Alan. Sorry, I wasn't clear in my message. I wasn't thinking
about including unmounted threads in the output of `Thread.print`, I
agree with you that besides the formatting things that still need to
be fixed there's no need to add more change
Thanks, Alan. Sorry, I wasn't clear in my message. I wasn't thinking about
including unmounted threads in the output of `Thread.print`, I agree with
you that besides the formatting things that still need to be fixed there's
no need to add more changes to the `Thread.print` command in the context of
On 04/06/2024 21:52, Iñigo Mediavilla wrote:
Hello,
While there's ongoing work on:
https://github.com/openjdk/jdk/pull/19482
to add the stack trace of mounted virtual threads to the `jcmd
Thread.print` command, I'm starting to think about how I could do to
print the stack trace for virtual
I looked through this, and I don’t think the there is anything needed other
than this PR. Eventually jstack creates a VM_PrintThreads command which calls
the threads.cpp code.
> On Jun 4, 2024, at 3:52 PM, Iñigo Mediavilla wrote:
>
> Hello,
>
> While there's ongoing work on:
>
> https://gith
Hello,
While there's ongoing work on:
https://github.com/openjdk/jdk/pull/19482
to add the stack trace of mounted virtual threads to the `jcmd
Thread.print` command, I'm starting to think about how I could do to print
the stack trace for virtual threads from `jstack` but I'm not sure about
what
