On Thu, 20 Jun 2024 11:58:23 GMT, Matthias Baesken wrote:
> The following issue has been observed when running
> serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorThreadTest (and some
> other :tier1 tests)
> on Linux with ubsan enabled binaries :
>
>
On Tue, 19 Mar 2024 20:15:18 GMT, Chris Plummer wrote:
>> So should I also use HeapDumpGzipLevel the same way as HeapDumpPath ? Tehn
>> we have to change the text in globals.hpp for HeapDumpGzipLevel as well
>> because it mentions only the HeapDumpOnOutOfmemoryError case and not the
>> jcmd
On Fri, 15 Mar 2024 06:59:42 GMT, Christoph Langer wrote:
>> src/hotspot/share/runtime/globals.hpp line 565:
>>
>>> 563: "triggered by jcmd GC.heap_dump without specifying a path, "
>>> \
>>> 564: "the path (filename or directory) of the dump file "
>>> \
On Thu, 14 Mar 2024 13:43:09 GMT, Matthias Baesken wrote:
>> Currently jcmd command GC.heap_dump only works with an additionally provided
>> file name.
>> Syntax : GC.heap_dump [options]
>>
>> In case the JVM has the XX - flag HeapDumpPath set, we should support an
>> additional mode where
