-
Bug
-
Resolution: Fixed
-
P4
-
15
-
b14
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8263869 | 13.0.7 | Yuri Nesterenko | P4 | Resolved | Fixed | b04 |
JDK-8248396 | 11.0.9-oracle | Kevin Walls | P4 | Resolved | Fixed | b01 |
JDK-8249023 | 11.0.9 | Kevin Walls | P4 | Resolved | Fixed | b01 |
JDK-8248562 | openjdk8u272 | Kevin Walls | P4 | Resolved | Fixed | b01 |
JDK-8248402 | 8u271 | Kevin Walls | P4 | Resolved | Fixed | b01 |
JDK-8251607 | emb-8u271 | Kevin Walls | P4 | Resolved | Fixed | team |
hs_err reports elapsed time in seconds.
Events are reported in 1/1000th of a second detail.
As second can be a long time, and we might want to know if the last Event logged happened a second ago, or 1/1000th of a second a go, i.e. "right now"?
hotspot/share/runtime/os.cpp
void os::print_date_and_time(outputStream *st, char* buf, size_t buflen) {
...
double t = os::elapsedTime();
// NOTE: It tends to crash after a SEGV if we want to printf("%f",...) in
// Linux. Must be a bug in glibc ? Workaround is to round "t" to int
// before printf. We lost some precision, but who cares?
int eltime = (int)t; // elapsed time in seconds
The comment came from before JDK 5 repo creation.
It's time to remove the slight on glibc here.
Events are reported in 1/1000th of a second detail.
As second can be a long time, and we might want to know if the last Event logged happened a second ago, or 1/1000th of a second a go, i.e. "right now"?
hotspot/share/runtime/os.cpp
void os::print_date_and_time(outputStream *st, char* buf, size_t buflen) {
...
double t = os::elapsedTime();
// NOTE: It tends to crash after a SEGV if we want to printf("%f",...) in
// Linux. Must be a bug in glibc ? Workaround is to round "t" to int
// before printf. We lost some precision, but who cares?
int eltime = (int)t; // elapsed time in seconds
The comment came from before JDK 5 repo creation.
It's time to remove the slight on glibc here.
- backported by
-
JDK-8248396 hs_err elapsed time in seconds is not accurate enough
- Resolved
-
JDK-8248402 hs_err elapsed time in seconds is not accurate enough
- Resolved
-
JDK-8248562 hs_err elapsed time in seconds is not accurate enough
- Resolved
-
JDK-8249023 hs_err elapsed time in seconds is not accurate enough
- Resolved
-
JDK-8251607 hs_err elapsed time in seconds is not accurate enough
- Resolved
-
JDK-8263869 hs_err elapsed time in seconds is not accurate enough
- Resolved
(1 backported by, 2 links to)