Decoder not properly initialized on Windows
volker.simonis at gmail.com
Fri Jul 15 03:42:49 PDT 2011
Ok, I don't want to appear to nit-picky, but a short
> hg log | grep "[0-9]/[0-9]"
7043298: 4/4 fix for 7028172 causes "Label too long: ..." error message
7041410: 5/4 finish removing SOLARIS_7_OR_LATER from HotSpot
7028172: 3/4 SA needs to adapt to Solaris libproc change made in 6748307
7039447: 2/1 java profiling is broken in build 139 (garbage in function name)
7010849: 5/5 Extraneous javac source/target options when building sa-jdi
reveals 36 changes which have a summary in this format.
So the severity/priority seems to be an integral part of the summary
field in this case.
That's of course no problem at all - it's just interesting to see that
some people/tools seem to insert the severity/priority right into the
But after you explained the meaning of the numbers the semantics is
now easily understandable.
On Fri, Jul 15, 2011 at 12:24 PM, David Holmes <David.Holmes at oracle.com> wrote:
> Volker Simonis said the following on 07/15/11 19:53:
>> But why do some bugs have these fields encoded in the Subject field
>> while others do not have them?
> I think it is simply the format used by the tool Dan used to show the bug
> <bug-id> <severity>/<priority> <synopsis>
>> On Fri, Jul 15, 2011 at 11:41 AM, Alan Bateman <Alan.Bateman at oracle.com>
>>> Volker Simonis wrote:
>>>> Thank you!
>>>> I'll file a webrev later today.
>>>> Just out of personal interest: can you explain to me what the numbers
>>>> (in this case '4/4') in front of the bug description mean. I see them
>>>> from time to time but couldn't figure out there meaning.
>>> The proprietary bug database has priority and severity fields so I assume
>>> this is priority=4 and severity=4 (where 1 is highest, 5 is lowest).
More information about the hotspot-runtime-dev