-
Bug
-
Resolution: Fixed
-
P3
-
25, 26
-
b08
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8362936 | 25.0.1 | Erik Gahlin | P3 | Resolved | Fixed | b03 |
| JDK-8362506 | 25 | Erik Gahlin | P3 | Resolved | Fixed | b33 |
The top frame in a stack trace for an I/O event should be where the user called the read or write method, for example, RandomAccessFile::readLong, and not a JDK internal method, such as FileRead::offer.
Other issues are, DataInputStream::readUTF(DataInput in), used by RandomAccessFile::readUTF(), and InputStream::readNBytes(byte[], int, int), which is not overridden by FileInputStream. (FileRead) and DataOutputStream::writeUTF(DataOutput) used by RandomAccessFile::writeUTF (FileWrite)
Other issues are, DataInputStream::readUTF(DataInput in), used by RandomAccessFile::readUTF(), and InputStream::readNBytes(byte[], int, int), which is not overridden by FileInputStream. (FileRead) and DataOutputStream::writeUTF(DataOutput) used by RandomAccessFile::writeUTF (FileWrite)
- backported by
-
JDK-8362506 JFR: Incorrect top frame for I/O events
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
- links to
-
Commit(jdk25)
openjdk/jdk/331adac3
-
Commit(master)
openjdk/jdk/1a6cbe42
-
Review(jdk25)
openjdk/jdk/26367
-
Review(master)
openjdk/jdk/26211
(2 links to)