serviceability-dev  

Messages by Thread

• • Re: RFR: 8379487: Dangling static ref to fallback error in libinstrument's JavaExceptions.c [v2] Kim Barrett
  • Integrated: 8379487: Dangling static ref to fallback error in libinstrument's JavaExceptions.c Joel Sikström
• Re: RFR: 8370691: Add new Float16Vector type and enable intrinsification of vector operations supported by auto-vectorizer [v28] Jatin Bhateja
• RFR: 8248165: Missing whitespace in jdb message printed when setting value of invalid type Alex Menkov
  • Re: RFR: 8248165: Missing whitespace in jdb message printed when setting value of invalid type Chris Plummer
  • Re: RFR: 8248165: Missing whitespace in jdb message printed when setting value of invalid type [v2] Alex Menkov
  • Re: RFR: 8248165: Missing whitespace in jdb message printed when setting value of invalid type [v2] Alex Menkov
  • Re: RFR: 8248165: Missing whitespace in jdb message printed when setting value of invalid type [v2] Chris Plummer
  • Integrated: 8248165: Missing whitespace in jdb message printed when setting value of invalid type Alex Menkov
• RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v2] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v3] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v3] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v3] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v3] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v3] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v3] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v4] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v5] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v6] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v6] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v7] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v7] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v7] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v8] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v8] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v8] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v8] Kevin Walls
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v8] Kevin Walls
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v8] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v8] Kevin Walls
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] Kevin Walls
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] Kevin Walls
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v9] Kevin Walls
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v10] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v11] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v11] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v11] Zhengyu Gu
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v11] David Holmes
  • Re: RFR: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) [v11] David Holmes
  • Integrated: 8323792: ThreadSnapshot::initialize can cause assert in Thread::check_for_dangling_thread_pointer (possibility of dangling Thread pointer) Zhengyu Gu
• RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! Yasumasa Suenaga
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! Yasumasa Suenaga
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation Martin Doerr
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! Chris Plummer
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! Yasumasa Suenaga
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v3] Chris Plummer
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v3] Yasumasa Suenaga
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! [v2] Yasumasa Suenaga
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! [v2] Yasumasa Suenaga
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! [v2] Fei Yang
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! [v2] Yasumasa Suenaga
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! [v2] Fei Yang
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! [v3] Yasumasa Suenaga
  • Re: RFR: 8378985: [lworld] serviceability/sa/TestJhsdbJstackMixedWithXComp.java#xcomp fails with just Test failed! [v3] David Holmes
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v3] Yasumasa Suenaga
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v3] Chris Plummer
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v4] Yasumasa Suenaga
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v4] Yasumasa Suenaga
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v4] Martin Doerr
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v4] Yasumasa Suenaga
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v5] Yasumasa Suenaga
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v5] Martin Doerr
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v5] Chris Plummer
  • Re: RFR: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation [v5] Fei Yang
  • Integrated: 8378985: serviceability/sa/TestJhsdbJstackMixedWithXComp.java failed if sender frame is return barrier of Continuation Yasumasa Suenaga
• Re: RFR: 8370691: Add new Float16Vector type and enable intrinsification of vector operations supported by auto-vectorizer [v27] Jatin Bhateja
• RFR: 8379371: Proposed cleanups for JDK-8373595 A new ObjectMonitorTable implementation Daniel D . Daugherty
  • Re: RFR: 8379371: Proposed cleanups for JDK-8373595 A new ObjectMonitorTable implementation Daniel D . Daugherty
  • Re: RFR: 8379371: Proposed cleanups for JDK-8373595 A new ObjectMonitorTable implementation Stefan Karlsson
  • Re: RFR: 8379371: Proposed cleanups for JDK-8373595 A new ObjectMonitorTable implementation Daniel D . Daugherty
  • Re: RFR: 8379371: Proposed cleanups for JDK-8373595 A new ObjectMonitorTable implementation Fredrik Bredberg
  • Integrated: 8379371: Proposed cleanups for JDK-8373595 A new ObjectMonitorTable implementation Daniel D . Daugherty
• Re: RFR: 8359706: Add file descriptor count to VM.info [v11] Kieran Farrell
  • Re: RFR: 8359706: Add file descriptor count to VM.info [v11] Thomas Stuefe
  • Re: RFR: 8359706: Add file descriptor count to VM.info [v11] Kieran Farrell
  • Re: RFR: 8359706: Add file descriptor count to VM.info [v11] Thomas Stuefe
  • Re: RFR: 8359706: Add file descriptor count to VM.info [v11] Kieran Farrell
• Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Afshin Zafari
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Robert Toyonaga
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Afshin Zafari
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Robert Toyonaga
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Afshin Zafari
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Robert Toyonaga
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Afshin Zafari
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Robert Toyonaga
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Robert Toyonaga
  • Re: RFR: 8353567: Tighten NMT lock scope in os::release_memory and os::uncommit_memory [v2] Afshin Zafari
• RFR: 8379193: Incorrect build ID path in SATestUtils.java Albert Mingkun Yang
  • Re: RFR: 8379193: Incorrect build ID path in SATestUtils.java [v2] Albert Mingkun Yang
  • Re: RFR: 8379193: Incorrect build ID path in SATestUtils.java [v2] Kevin Walls
  • Re: RFR: 8379193: Incorrect build ID path in SATestUtils.java [v2] Yasumasa Suenaga
  • Re: RFR: 8379193: Incorrect build ID path in SATestUtils.java [v2] Albert Mingkun Yang
  • Integrated: 8379193: Incorrect build ID path in SATestUtils.java Albert Mingkun Yang
• Re: RFR: 8370691: Add new Float16Vector type and enable intrinsification of vector operations supported by auto-vectorizer [v26] Jatin Bhateja
• [External] : [NEED HELP] Check `jhsdb jstack --mixed` behavior on each port projects suenaga
• RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Oli Gillespie
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Kevin Walls
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Kevin Walls
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Oli Gillespie
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Kevin Walls
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Oli Gillespie
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed David Holmes
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Kevin Walls
  • Re: RFR: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed duke
  • Integrated: 8378963: Test test/jdk/java/lang/management/RuntimeMXBean/InputArgument.java#id4 failed Oli Gillespie
• RFR: 8378854: Disable SA tests when ZGC is being used Chris Plummer
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] Chris Plummer
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] Yasumasa Suenaga
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] SendaoYan
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] Chris Plummer
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] Kevin Walls
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] SendaoYan
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] Stefan Karlsson
  • Re: RFR: 8378854: Disable SA tests when ZGC is being used [v2] Chris Plummer
  • Integrated: 8378854: Disable SA tests when ZGC is being used Chris Plummer
• Re: RFR: 8302745: sp > unextended_sp for interpreted to interpreted calls going through method handle linker [v2] Dean Long
  • Re: RFR: 8302745: sp > unextended_sp for interpreted to interpreted calls going through method handle linker [v2] Andrew Haley
  • Re: RFR: 8302745: sp > unextended_sp for interpreted to interpreted calls going through method handle linker [v2] Anton Artemov
  • Re: RFR: 8302745: sp > unextended_sp for interpreted to interpreted calls going through method handle linker [v2] Anton Artemov
  • Re: RFR: 8302745: sp > unextended_sp for interpreted to interpreted calls going through method handle linker [v2] Dean Long
  • Re: RFR: 8302745: sp > unextended_sp for interpreted to interpreted calls going through method handle linker [v2] Anton Artemov
• Re: RFR: 8370691: Add new Float16Vector type and enable intrinsification of vector operations supported by auto-vectorizer [v25] Jatin Bhateja
• RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type Jasmine Karthikeyan
  • Re: RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type Luca Kellermann
  • Re: RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type Daniel Jeliński
  • Re: RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type [v2] Jasmine Karthikeyan
  • Re: RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type [v2] Jasmine Karthikeyan
  • Re: RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type [v2] Daniel Jeliński
  • Re: RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type [v2] Alan Bateman
  • Re: RFR: 8378180: Compiling OpenJDK with C23 C-Compiler gives warning: initialization discards ‘const’ qualifier from pointer target type Jasmine Karthikeyan
• Re: RFR: 8302745: sp > unextended_sp for interpreted to interpreted calls going through method handle linker Serguei Spitsyn
• RFR: 8378641: Test serviceability/jvmti/RedefineClasses/RedefineVerifyError.java‎ missing UnlockDiagnosticVMOptions after 8376295 Leonid Mesnik
  • Re: RFR: 8378641: Test serviceability/jvmti/RedefineClasses/RedefineVerifyError.java‎ missing UnlockDiagnosticVMOptions after 8376295 Albert Mingkun Yang
  • Re: RFR: 8378641: Test serviceability/jvmti/RedefineClasses/RedefineVerifyError.java‎ missing UnlockDiagnosticVMOptions after 8376295 David Holmes
  • Re: RFR: 8378641: Test serviceability/jvmti/RedefineClasses/RedefineVerifyError.java‎ missing UnlockDiagnosticVMOptions after 8376295 SendaoYan
  • Integrated: 8378641: Test serviceability/jvmti/RedefineClasses/RedefineVerifyError.java‎ missing UnlockDiagnosticVMOptions after 8376295 Leonid Mesnik
• Integrated: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote Leonid Mesnik
• RFR: 8378549: Incorrect assert in JvmtiThreadState::update_for_pop_top_frame Serguei Spitsyn
  • Re: RFR: 8378549: Incorrect assert in JvmtiThreadState::update_for_pop_top_frame Leonid Mesnik
  • Re: RFR: 8378549: Incorrect assert in JvmtiThreadState::update_for_pop_top_frame Serguei Spitsyn
  • Integrated: 8378549: Incorrect assert in JvmtiThreadState::update_for_pop_top_frame Serguei Spitsyn
• Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote [v2] Leonid Mesnik
  • Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote [v2] David Holmes
  • Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote [v2] Coleen Phillimore
• Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote Serguei Spitsyn
  • Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote Coleen Phillimore
  • Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote [v2] Leonid Mesnik
  • Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote [v2] David Holmes
  • Re: RFR: 8376295: "assert(BytecodeVerificationRemote) failed: Should not be here" when running class redefinition test with -XX:-BytecodeVerificationRemote Coleen Phillimore
• Integrated: 8376125: Out of memory in the CDS archive error with lot of classes Xue-Lei Andrew Fan
• RFR: 8378369: TestJhsdbJstackMixedWithVDSOCallCore.java fails if missing vdso64.so Yasumasa Suenaga
  • Re: RFR: 8378369: TestJhsdbJstackMixedWithVDSOCallCore.java fails if missing vdso64.so Chris Plummer
  • Re: RFR: 8378369: TestJhsdbJstackMixedWithVDSOCallCore.java fails if missing vdso64.so Yasumasa Suenaga
  • Re: RFR: 8378369: TestJhsdbJstackMixedWithVDSOCallCore.java fails if missing vdso64.so Chris Plummer
  • Re: RFR: 8378369: TestJhsdbJstackMixedWithVDSOCallCore.java fails if missing vdso64.so Albert Mingkun Yang
  • Integrated: 8378369: TestJhsdbJstackMixedWithVDSOCallCore.java fails if missing vdso64.so Yasumasa Suenaga
• RFR: 8377671: Step Over doesn't stop after receiving MethodExitEvent Chris Plummer
  • Re: RFR: 8377671: Step Over doesn't stop after receiving MethodExitEvent Serguei Spitsyn
  • Re: RFR: 8377671: Step Over doesn't stop after receiving MethodExitEvent Alex Menkov
  • Re: RFR: 8377671: Step Over doesn't stop after receiving MethodExitEvent Chris Plummer
  • Integrated: 8377671: Step Over doesn't stop after receiving MethodExitEvent Chris Plummer
• RFR: 8373944: ObjectMonitor::ExitOnSuspend can call java_lang_VirtualThread::set_onWaitingList() while in safepoint Patricio Chilano Mateo
  • Re: RFR: 8373944: ObjectMonitor::ExitOnSuspend can call java_lang_VirtualThread::set_onWaitingList() while in safepoint David Holmes
  • Re: RFR: 8373944: ObjectMonitor::ExitOnSuspend can call java_lang_VirtualThread::set_onWaitingList() while in safepoint Patricio Chilano Mateo
  • Re: RFR: 8373944: ObjectMonitor::ExitOnSuspend can call java_lang_VirtualThread::set_onWaitingList() while in safepoint Fredrik Bredberg
  • Integrated: 8373944: ObjectMonitor::ExitOnSuspend can call java_lang_VirtualThread::set_onWaitingList() while in safepoint Patricio Chilano Mateo
• Integrated: 8377729: Running jtreg tests with -agent... option causes some tests to fail due to duplicate -agent options provided to a subprocess Kirill Shirokov
• Re: RFR: 8370691: Add new Float16Vector type and enable intrinsification of vector operations supported by auto-vectorizer [v24] Jatin Bhateja
• RFR: 8377433: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java failed Kevin Walls
  • Re: RFR: 8377433: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java failed Serguei Spitsyn
  • Re: RFR: 8377433: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java failed Kevin Walls
  • Integrated: 8377433: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java failed Kevin Walls
• Re: RFR: 8370691: Add new Float16Vector type and enable intrinsification of vector operations supported by auto-vectorizer [v23] Jatin Bhateja
• Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Xue-Lei Andrew Fan
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Ioi Lam
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Ioi Lam
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Xue-Lei Andrew Fan
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Ioi Lam
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Jiangli Zhou
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Xue-Lei Andrew Fan
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Jiangli Zhou
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v11] Ashutosh Mehra
• Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v10] Xue-Lei Andrew Fan
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v10] Ashutosh Mehra
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v10] Ioi Lam
  • Re: RFR: 8376125: Out of memory in the CDS archive error with lot of classes [v10] Ashutosh Mehra
• RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out Serguei Spitsyn
  • Re: RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out Patricio Chilano Mateo
  • Re: RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out Serguei Spitsyn
  • Re: RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out Patricio Chilano Mateo
  • Re: RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out [v2] Serguei Spitsyn
  • Re: RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out Serguei Spitsyn
  • Re: RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out [v2] Serguei Spitsyn
  • Re: RFR: 8375457: Test serviceability/jvmti/vthread/SelfSuspendDisablerTest/SelfSuspendDisablerTest.java#default timed out [v2] Patricio Chilano Mateo

• Earlier messages
• Later messages