-
Bug
-
Resolution: Duplicate
-
P4
-
hs25, 5.0u4, 6u10, 7, 8
-
generic
-
generic
jmap prints logging into stderr instead of stdout:
Attaching to process ID 9552, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 12.0-b01
finding class loader instances ...
However note it does not print them, for example, for jmap -histo on live process (?).
In addition, there is jmap-specific debugging output which does not seem to be relevant to anything:
Finding object size using Printezis bits and skipping over...
Finding object size using Printezis bits and skipping over...
(multiple lines)
Attaching to process ID 9552, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 12.0-b01
finding class loader instances ...
However note it does not print them, for example, for jmap -histo on live process (?).
In addition, there is jmap-specific debugging output which does not seem to be relevant to anything:
Finding object size using Printezis bits and skipping over...
Finding object size using Printezis bits and skipping over...
(multiple lines)
- duplicates
-
JDK-6626412 jstack using SA prints some info messages into err stream
- Resolved
-
JDK-6626412 jstack using SA prints some info messages into err stream
- Resolved
- relates to
-
JDK-6605919 jinfo incorrect usage of stderr, exit codes
- Closed
-
JDK-6626412 jstack using SA prints some info messages into err stream
- Resolved