serviceability-dev  

Messages by Thread

• • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] Albert Mingkun Yang
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] Albert Mingkun Yang
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] Stefan Johansson
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v10] David Holmes
• Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v9] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v9] Stefan Johansson
• Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v8] Jonas Norlinder
• Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v7] Jonas Norlinder
• Send attach request even though SigCgt is not set Yasumasa Suenaga
  • Re: Send attach request even though SigCgt is not set Laurence Cable
• Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v6] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v6] Jonas Norlinder
• Re: RFR: 8358890: VM option -XX:AllowRedefinitionToAddDeleteMethods should be obsoleted then expired [v8] Serguei Spitsyn
• RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Chris Plummer
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 SendaoYan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 SendaoYan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Serguei Spitsyn
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Andrey Turbanov
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v2] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Erik Joelsson
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v2] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v2] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v2] Doug Simon
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v2] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] SendaoYan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] SendaoYan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] David Holmes
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] David Holmes
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] SendaoYan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] David Holmes
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] SendaoYan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] SendaoYan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Daniel Fuchs
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Roger Riggs
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v3] Leonid Mesnik
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Daniel Fuchs
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] David Holmes
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Magnus Ihse Bursie
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Magnus Ihse Bursie
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] David Holmes
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v4] Magnus Ihse Bursie
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Magnus Ihse Bursie
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Phil Race
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] David Holmes
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Phil Race
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Albert Mingkun Yang
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Alan Bateman
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Albert Mingkun Yang
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] David Holmes
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Albert Mingkun Yang
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Matthew Donovan
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v6] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v5] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v6] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v7] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v8] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v9] Leo Korinth
  • Re: RFR: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 [v9] Alan Bateman
  • Integrated: 8260555: Change the default TIMEOUT_FACTOR from 4 to 1 Leo Korinth
• Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Albert Mingkun Yang
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Stefan Johansson
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Stefan Johansson
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Albert Mingkun Yang
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Jonas Norlinder
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Stefan Johansson
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Albert Mingkun Yang
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Stefan Johansson
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Albert Mingkun Yang
  • Re: RFR: 8364638: Refactor and make accumulated GC CPU time code generic [v5] Jonas Norlinder
• Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v2] Gerard Ziemski
  • Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v2] David Holmes
  • Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v3] Sergey Chernyshev
  • Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v3] David Holmes
  • Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v4] Sergey Chernyshev
  • Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v2] Serguei Spitsyn
  • Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v2] Sergey Chernyshev
  • Re: RFR: 8319589: Attach from root to a user java process not supported in Mac [v2] Larry Cable
• Re: RFR: 8318706: Implement JEP 423: Region Pinning for G1 [v10] Cheng Pan
• RFR: 8365264: Rename ResourceHashtable to HashTable Johan Sjölen
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable Johan Sjölen
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v2] Johan Sjölen
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v3] Johan Sjölen
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v4] Johan Sjölen
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v4] Albert Mingkun Yang
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v4] Ioi Lam
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v4] Johan Sjölen
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v5] Johan Sjölen
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v5] Ioi Lam
  • Re: RFR: 8365264: Rename ResourceHashtable to HashTable [v5] Johan Sjölen
  • Integrated: 8365264: Rename ResourceHashtable to HashTable Johan Sjölen
• RFR: 8365240: [asan] exclude some tests when using asan enabled binaries Matthias Baesken
  • Re: RFR: 8365240: [asan] exclude some tests when using asan enabled binaries Leonid Mesnik
  • Re: RFR: 8365240: [asan] exclude some tests when using asan enabled binaries Serguei Spitsyn
  • Re: RFR: 8365240: [asan] exclude some tests when using asan enabled binaries Matthias Baesken
  • Integrated: 8365240: [asan] exclude some tests when using asan enabled binaries Matthias Baesken
• RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v2] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v2] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v2] Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v2] Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v3] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Patricio Chilano Mateo
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Serguei Spitsyn
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Patricio Chilano Mateo
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v6] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v6] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v8] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v9] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v10] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v10] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v11] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v12] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v13] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v13] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v13] Patricio Chilano Mateo
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v13] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v13] Leonid Mesnik
  • Withdrawn: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Leonid Mesnik
  • RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v2] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v3] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v3] David Holmes
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v3] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v6] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Martin Doerr
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v5] Martin Doerr
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] Martin Doerr
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v7] David Holmes
  • Integrated: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v8] Leonid Mesnik
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v8] Martin Doerr
  • Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v4] Leonid Mesnik
• RFR: 8364281: Reduce JNI usage in Linux attach provider Philippe Marschall
  • Re: RFR: 8364281: Reduce JNI usage in Linux attach provider Sebastian Lövdahl
  • Re: RFR: 8364281: Reduce JNI usage in Linux attach provider Philippe Marschall
• RFR: 8365184: sun/tools/jhsdb/HeapDumpTestWithActiveProcess.java Re-enable SerialGC flag on debuggee process Ramkumar Sunderbabu
  • Re: RFR: 8365184: sun/tools/jhsdb/HeapDumpTestWithActiveProcess.java Re-enable SerialGC flag on debuggee process Leonid Mesnik
  • Re: RFR: 8365184: sun/tools/jhsdb/HeapDumpTestWithActiveProcess.java Re-enable SerialGC flag on debuggee process Chris Plummer
  • Re: RFR: 8365184: sun/tools/jhsdb/HeapDumpTestWithActiveProcess.java Re-enable SerialGC flag on debuggee process duke
  • Re: RFR: 8365184: sun/tools/jhsdb/HeapDumpTestWithActiveProcess.java Re-enable SerialGC flag on debuggee process Serguei Spitsyn

• Earlier messages
• Later messages