Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 6
Affects Version/s: 5.0u6, 6
Component/s: core-libs
Labels:
- mustang-low

Subcomponent:
java.lang:reflect
Resolved In Build:
b63
CPU:

generic
OS:

generic

The modifier bit position for the bridge flag on a method is the same as the bit position for the volatile property of a field. Currently if Method.toString is called on a bridge method the "volatile" property will inappropriately appear. There is a similar overlap between the var-args and transient bits.

duplicates

JDK-6362451 the string returned by toString() shows the bridge methods as having the volatile modificator

Closed

relates to

JDK-6992717 methods inherited from non-public super class are volatile

Closed

JDK-6261502 (reflect) Add the functionality to screen out the "inappropriate" modifier bits

Resolved

JDK-8266670 Better modeling of access flags in core reflection

Resolved

JDK-6316717 (reflect) Method.toGenericString prints out inappropriate modifiers

Closed

JDK-6516895 Varargs argument to method or ctor sets 'transient' modifier

Closed

(1 relates to)

Assignee:: Joe Darcy

Reporter:: Joe Darcy

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 2005-11-22 13:42

Updated:: 2021-05-06 15:13

Resolved:: 2005-12-02 22:09

Imported:: 15/Sep/12 11:21 PM

Indexed:: 17/Jul/12 7:41 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates