gc.log with faulty ParNew

[Jon Masamitsu]

On 11/08/11 10:59, Charles K Pepperdine wrote:
> Jon,
>
> I've been looking at the logging and I'd say that there is plenty of 
> room to build something that would sort out the difficulties. And, I'd 
> be happy to dig in and help fix it but unfortunately I've got no free 
> cycles to do so at the moment. I guess that's been the difficulty, no 
> one has had the free cycles to dig in.

Lack of time is indeed the barrier.  If you do decide to look into it,
give us a heads up.  I can try and dig up some notes on some
modifications to the format that we thought would make the
output more parsable.  Also there is something in the works
that has to do with standardizing the logging within hotspot.
I don't know the details but I can ask around if you (or anyone)
has a chance to put in time on this.

Jon

>
> Regards,
> Kirk
>
> On Nov 8, 2011, at 5:22 PM, Jon Masamitsu wrote:
>
>> Kirk,
>>
>> Sorry but there is nothing I'm aware of that will fix this
>> problem with the current way of doing logging.   It plagues
>> us as much as anyone but no one has screamed "I can't
>> take it anymore"  and fixed it.
>>
>> Jon
>>
>> On 11/07/11 13:49, Charles K Pepperdine wrote:
>>> Hi all,
>>>
>>> Line 15 of this log file has a ParNew record split by the end or an 
>>> abortable-preclean. Is there a way to prevent the gc log records 
>>> from being corrupted in this way? This is not the only place it 
>>> happens and it makes an already impossible task of scanning these 
>>> things much harder.
>>>
>>> Regards,
>>> Kirk
>>>
>>>
>>> Begin forwarded message:
>>>
>>> =
>>>
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20111108/3a83c818/attachment.htm>