serviceability-dev  

Messages by Thread

• [External] : Proposal: young-only heap dumps Gillespie, Oli
  • Re: [External] : Proposal: young-only heap dumps Erik Gahlin
  • Re: [External] : Proposal: young-only heap dumps Gillespie, Oli
• RFR: 8390009: FieldAccess and FieldModification events should be suppressed during strict initialization Alan Bateman
  • Withdrawn: 8390009: FieldAccess and FieldModification events should be suppressed during strict initialization Alan Bateman
• RFR: 8396201: VM_HeapWalkOperation::visit can mistake a flattened value for its ClassLoader holder Serguei Spitsyn
  • Re: RFR: 8396201: VM_HeapWalkOperation::visit can mistake a flattened value for its ClassLoader holder Serguei Spitsyn
  • Re: RFR: 8396201: VM_HeapWalkOperation::visit can mistake a flattened value for its ClassLoader holder [v2] Serguei Spitsyn
  • Re: RFR: 8396201: VM_HeapWalkOperation::visit can mistake a flattened value for its ClassLoader holder [v2] Stefan Karlsson
  • Re: RFR: 8396201: VM_HeapWalkOperation::visit can mistake a flattened value for its ClassLoader holder Stefan Karlsson
  • Re: RFR: 8396201: VM_HeapWalkOperation::visit can mistake a flattened value for its ClassLoader holder [v2] Serguei Spitsyn
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v50] Kevin Walls
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v49] Kevin Walls
• Re: RFR: 8374364: TestCgroupMetrics.java fails when cpuset unmounted [v18] Sendao Yan
• Re: RFR: 8374364: TestCgroupMetrics.java fails when cpuset unmounted [v17] Sendao Yan
• RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Koichi Sakata
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Yasumasa Suenaga
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Koichi Sakata
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Yasumasa Suenaga
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Koichi Sakata
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Yasumasa Suenaga
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Koichi Sakata
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found Yasumasa Suenaga
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found [v2] Koichi Sakata
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found [v2] Yasumasa Suenaga
  • Re: RFR: 8386291: serviceability/sa/ClhsdbPstack.java#core fails with DebuggerException: DWARF not found [v2] Koichi Sakata
• RFR: 8397000: find_initial_Java_frame should return false for the first frame of upcall Xin Liu
  • Re: RFR: 8397000: find_initial_Java_frame should return false for the first frame of upcall [v2] Xin Liu
• Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v20] Kieran Farrell
  • Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v20] Sean Coffey
  • Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v20] Kevin Walls
• Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v19] Kieran Farrell
  • Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v19] Sean Coffey
  • Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v19] Kieran Farrell
  • Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v19] Alan Bateman
  • Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v19] Kieran Farrell
• Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v18] Kieran Farrell
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v48] Kevin Walls
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v48] Alan Bateman
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v48] Kevin Walls
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v48] Alan Bateman
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v48] Kevin Walls
• RFR: 8396859: SA should refer PT_NOTE to obtain Build ID Yasumasa Suenaga
  • Re: RFR: 8396859: SA should refer PT_NOTE to obtain Build ID [v2] Yasumasa Suenaga
  • Re: RFR: 8396859: SA should refer PT_NOTE to obtain Build ID [v2] Erik Joelsson
  • Re: RFR: 8396859: SA should refer PT_NOTE to obtain Build ID [v2] Chris Plummer
  • Re: RFR: 8396859: SA should refer PT_NOTE to obtain Build ID [v2] Yasumasa Suenaga
  • Re: RFR: 8396859: SA should refer PT_NOTE to obtain Build ID [v3] Yasumasa Suenaga
  • Re: RFR: 8396859: SA should refer PT_NOTE to obtain Build ID [v3] Chris Plummer
  • Re: RFR: 8396859: SA should refer PT_NOTE to obtain Build ID [v3] Yasumasa Suenaga
• RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v2] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v2] David Holmes
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v2] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Vladimir Kozlov
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v4] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v5] Vladimir Kozlov
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Vladimir Kozlov
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Vladimir Kozlov
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Vladimir Kozlov
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v3] Leonid Mesnik
  • Integrated: 8396399: VMObjectAlloc is not called from clone() intrinsic Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v5] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v5] Vladimir Kozlov
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v5] Serguei Spitsyn
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v5] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v4] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v6] Leonid Mesnik
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v6] Vladimir Kozlov
  • Re: RFR: 8396399: VMObjectAlloc is not called from clone() intrinsic [v6] Serguei Spitsyn
• RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache Ioi Lam
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache Jean-Noël Rouvignac
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache Jean-Noël Rouvignac
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v2] Ioi Lam
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v2] Ioi Lam
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v2] Vladimir Kozlov
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v2] Ioi Lam
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v2] Vladimir Kozlov
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v2] Ioi Lam
  • Integrated: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache Ioi Lam
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v3] Ioi Lam
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v3] Ashutosh Mehra
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v3] Vladimir Kozlov
  • Re: RFR: 8396738: Clean up C++ APIs for accessing AOT configuration and AOT cache [v3] Ioi Lam
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v47] Kevin Walls
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v47] Kevin Walls
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v46] Kevin Walls
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v45] Kevin Walls
• Re: RFR: 8380361: Display -XshowSettings configuration data via jcmd [v17] Kieran Farrell
• RFR: 8395705: Remove support for GXL heap dumps Yasumasa Suenaga
  • Re: RFR: 8395705: Remove support for GXL heap dumps Chris Plummer
  • Re: RFR: 8395705: Remove support for GXL heap dumps Yasumasa Suenaga
  • Integrated: 8395705: Remove support for GXL heap dumps Yasumasa Suenaga
  • Re: RFR: 8395705: Remove support for GXL heap dumps Kevin Walls
• RFR: 8396655: Build conflict when 8394161 and 8381370 was integrated Stefan Karlsson
  • Integrated: 8396655: Build conflict when 8394161 and 8381370 was integrated Stefan Karlsson
  • Re: RFR: 8396655: Build conflict when 8394161 and 8381370 was integrated Aleksey Shipilev
  • Re: RFR: 8396655: Build conflict when 8394161 and 8381370 was integrated Stefan Karlsson
  • Re: RFR: 8396655: Build conflict when 8394161 and 8381370 was integrated Stefan Karlsson
  • Re: RFR: 8396655: Build conflict when 8394161 and 8381370 was integrated Erik Österlund
• RFR: 8392584: Improve JFR tracking of JVMTI agent lifetimes Markus Grönlund
  • Re: RFR: 8392584: Improve JFR tracking of JVMTI agent lifetimes Erik Joelsson
  • Re: RFR: 8392584: Improve JFR tracking of JVMTI agent lifetimes [v2] Markus Grönlund
  • Re: RFR: 8392584: Improve JFR tracking of JVMTI agent lifetimes [v2] Erik Joelsson
  • Re: RFR: 8392584: Improve JFR tracking of JVMTI agent lifetimes [v2] Markus Grönlund
• RFR: 8396520: SA: Align continuation entry size when computing frame pointers Gui Cao
  • Integrated: 8396520: SA: Align continuation entry size when computing frame pointers Gui Cao
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers [v3] Gui Cao
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers [v3] Chris Plummer
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers [v3] Yasumasa Suenaga
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers [v3] Gui Cao
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers [v3] Gui Cao
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers Chris Plummer
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers Gui Cao
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers [v3] Gui Cao
  • Re: RFR: 8396520: SA: Align continuation entry size when computing frame pointers [v2] Gui Cao
• RFR: 8396443: TestLongAltRootPath fails on macOS after JDK-8391991 Matthias Baesken
  • Re: RFR: 8396443: TestLongAltRootPath fails on macOS after JDK-8391991 Chris Plummer
  • Integrated: 8396443: TestLongAltRootPath fails on macOS after JDK-8391991 Matthias Baesken
  • Re: RFR: 8396443: TestLongAltRootPath fails on macOS after JDK-8391991 Matthias Baesken
• [External] : Virtual Serviceability Meetup 2026 Marcus Hirt
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Kevin Walls
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Chris Plummer
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Kevin Walls
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Kevin Walls
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Chris Plummer
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Kevin Walls
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Fei Yang
  • Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v44] Kevin Walls
• RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector Chris Plummer
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v4] Emanuel Peter
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v4] Emanuel Peter
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v3] Chris Plummer
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v3] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] Chris Plummer
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] Chris Plummer
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] Emanuel Peter
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] Chris Plummer
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] Emanuel Peter
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] Emanuel Peter
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v2] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v4] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v4] Emanuel Peter
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v3] jonghoonpark
  • Re: RFR: 8394577: VectorAPI: Serviceability agent is missing type support for Location::vector [v3] Chris Plummer
• Re: RFR: 8344159: Add lint warnings for unnecessary warning suppression [v19] Archie Cobbs
• RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently Yasumasa Suenaga
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently Fei Yang
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently Yasumasa Suenaga
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v2] Yasumasa Suenaga
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v2] Martin Doerr
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v2] Yasumasa Suenaga
  • Integrated: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently Yasumasa Suenaga
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v4] Yasumasa Suenaga
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v4] Yasumasa Suenaga
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v4] Chris Plummer
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v4] Serguei Spitsyn
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v3] Yasumasa Suenaga
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v3] Chris Plummer
  • Re: RFR: 8396232: TestJhsdbJstackWithVirtualThread.java reports UnalignedAddressException silently [v3] Yasumasa Suenaga
• Re: RFR: 8378084: Implement JEP 528: Post-Mortem Crash Analysis with jcmd [v43] Kevin Walls
• RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 Long Yang
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 Yasumasa Suenaga
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v2] Long Yang
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] Long Yang
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v2] Long Yang
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] Long Yang
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] Yasumasa Suenaga
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] duke
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] Long Yang
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] Chris Plummer
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] Long Yang
  • Re: RFR: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 [v3] Chris Plummer
  • Integrated: 8395826: Use PC - 1 for DWARF lookup of native return addresses in mixed jstack on Linux AMD64 and AArch64 Long Yang
• RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads Shiv Shah
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads Serguei Spitsyn
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads [v2] Shiv Shah
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads [v2] Shiv Shah
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads [v2] Serguei Spitsyn
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads [v2] Leonid Mesnik
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads [v2] Shiv Shah
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads [v3] Shiv Shah
  • Re: RFR: 8308026: AsyncGetCallTraceTest fails with virtual threads [v3] Leonid Mesnik
• RFR: 8396046: Leaks after failing to attach a JVM TI agent Timofei Pushkin
  • Re: RFR: 8396046: Leaks after failing to attach a JVM TI agent Timofei Pushkin
  • Re: RFR: 8396046: Leaks after failing to attach a JVM TI agent David Holmes
  • Re: RFR: 8396046: Leaks after failing to attach a JVM TI agent Timofei Pushkin
  • Re: RFR: 8396046: Leaks after failing to attach a JVM TI agent [v2] Timofei Pushkin
  • Re: RFR: 8396046: Leaks after failing to attach a JVM TI agent [v2] Timofei Pushkin
  • Re: RFR: 8396046: Leaks after failing to attach a JVM TI agent [v2] David Holmes
  • Re: RFR: 8396046: Leaks after failing to attach a JVM TI agent [v2] Serguei Spitsyn

• Earlier messages