Integrated: 8335743: jhsdb jstack cannot print some information on the waiting thread

On Fri, 5 Jul 2024 09:23:21 GMT, KIRIYAMA Takuya wrote: > This bug was introduced by JDK-8284161. "Object.wait (long timeoutMillis)" > was changed to call "Object.wait0 (long timeoutMillis)" in JDK-8284161. > > When "jhdsb jstack" is executed, the st

Re: RFR: 8335743: jhsdb jstack cannot print some information on the waiting thread [v2]

On Mon, 8 Jul 2024 12:16:51 GMT, KIRIYAMA Takuya wrote: >> This bug was introduced by JDK-8284161. "Object.wait (long timeoutMillis)" >> was changed to call "Object.wait0 (long timeoutMillis)" in JDK-8284161. >> >> When "jhdsb jstack" i

Re: RFR: 8335743: jhsdb jstack cannot print some information on the waiting thread [v2]

On Mon, 8 Jul 2024 06:52:34 GMT, David Holmes wrote: >> KIRIYAMA Takuya has updated the pull request incrementally with one >> additional commit since the last revision: >> >> 8335743: jhsdb jstack cannot print some information on the waiting thread > > test/h

Re: RFR: 8335743: jhsdb jstack cannot print some information on the waiting thread [v2]

ait0 (...)". > I confirmed that the lock information is correctly printed with this fix. > I tested hotspot/jtreg/serviceability/sa/ and > jdk/sun/tools/jhsdb/heapconfig/, and there were no regressions by this fix. > > Would anyone review this change, please? KIRIYAMA

RFR: 8335743: jhsdb jstack cannot print some information on the waiting thread

This bug was introduced by JDK-8284161. "Object.wait (long timeoutMillis)" was changed to call "Object.wait0 (long timeoutMillis)" in JDK-8284161. When "jhdsb jstack" is executed, the stack and lock information are printed in "sun.jvm.hotspot.runtime.JavaVFrame.printLockInfo(PrintStream tty, int

Integrated: 8290497: some tests in com/sun/jdi fail on localized Windows platform

On Tue, 19 Jul 2022 06:30:09 GMT, KIRIYAMA Takuya wrote: > Failed tests call java.lang.ProcessBuilder in direct, so not used command > options specified when jtreg command run. > To run non-localized tests, the locale options should be added in > ProcessBuilder. > > Could y

Re: RFR: 8290497: some tests in com/sun/jdi fail on localized Windows platform [v2]

On Wed, 20 Jul 2022 07:41:42 GMT, Serguei Spitsyn wrote: >> @sspitsyn >> Thank you for your review. Coud you integrate this fix, please? > > @tkiriyama Normally, two reviews are required in Serviceability area. @sspitsyn Can I ask you again to integrate this fix? - PR: https://git

Re: RFR: 8290497: some tests in com/sun/jdi fail on localized Windows platform

On Wed, 20 Jul 2022 20:47:31 GMT, Chris Plummer wrote: >> Failed tests call java.lang.ProcessBuilder in direct, so not used command >> options specified when jtreg command run. >> To run non-localized tests, the locale options should be added in >> ProcessBuilder. >> >> Could you review this

Re: RFR: 8290497: some tests in com/sun/jdi fail on localized Windows platform [v2]

> Failed tests call java.lang.ProcessBuilder in direct, so not used command > options specified when jtreg command run. > To run non-localized tests, the locale options should be added in > ProcessBuilder. > > Could you review this fix, please? KIRIYAMA Takuya has update

Re: RFR: 8290497: some tests in com/sun/jdi fail on localized Windows platform

On Tue, 19 Jul 2022 23:36:33 GMT, Serguei Spitsyn wrote: >> Failed tests call java.lang.ProcessBuilder in direct, so not used command >> options specified when jtreg command run. >> To run non-localized tests, the locale options should be added in >> ProcessBuilder. >> >> Could you review thi

RFR: 8290497: some tests in com/sun/jdi fail on localized Windows platform

Failed tests call java.lang.ProcessBuilder in direct, so not used command options specified when jtreg command run. To run non-localized tests, the locale options should be added in ProcessBuilder. Could you review this fix, please? - Commit messages: - 8290497: some tests in com