RFR: 8154791: Xlog classload too redundant msgs info/debug

[Thomas Stüfe]

On Wed, May 3, 2017 at 9:03 AM, Marcus Larsson <marcus.larsson at oracle.com>
wrote:

> Hi,
>
>
> On 2017-05-03 08:23, Thomas Stüfe wrote:
>
>> Hi Ioi,
>>
>> On Tue, May 2, 2017 at 11:10 PM, Ioi Lam <ioi.lam at oracle.com> wrote:
>>
>> By the way, I think we should really fix this in the UL level -- have
>>> multi-line buffering, so you can prevent other threads from interleaving
>>> your input. Make it something like:
>>>
>>>      Log(class, load).start_buffering();
>>>      log_info(class, load)(class name and source);
>>>      log_debug(class, load)(other details);
>>>      Log(class, load).flush();
>>>
>>> That way, the output will look like this:
>>>
>>> [0.162s][debug ][class,load] java.lang.Comparable source: jrt:/java.base
>>> [0.162s][debug ][class,load] [NULL class_loader] 0x00000007c00013a8
>>> super:
>>> 0x00000007c0000fb0 bytes: 235 checksum: a75dadb6
>>>
>>> So the output will be terse, and still parsable.
>>>
>>> I think this will be useful for other types of logs as well, not just the
>>> class loading logs.
>>>
>>>
>>> I thought that already exists:
>>
>> https://bugs.openjdk.java.net/browse/JDK-8145934
>>
>> see logMessage.hpp.
>>
>> Kind Regards, Thomas
>>
>
> Indeed it does. Thanks for pointing that out, Thomas.
>
>
Thanks for implementing it :)

..Thomas


> Marcus
>