In diagnosticCommand.cpp you'll want to use "res != 0"
on lines 1084 and 1086 to avoid compiler warnings
about ambiguous conversions to boolean.
1082 // The result should be a byte array or null
1083 typeArrayOop res = (typeArrayOop) result.get_jobject();
1084 assert(!res || (TypeArrayKlass::cast(res->klass())->element_type() == T_BYTE),
"Must be byte array");
1085
1086 if (res&& (res->length()> 0)) {
I see a SEGV in print_debug_listen_address running
GetListenAddressTest with a linux-x64-debug build.
Can you triage the bug and target the fixVersion for 13.
Thanks
On 4/29/19, 9:19 AM, Schmelter, Ralf wrote:
Please review the patch which adds a jcmd to get the actual address the
debugging backend is listening on.
The this value was stored in the agent property sun.jdwp.listenerAddress and
currently only used by the ProcessAttachingConnector.
Additionally, the listen address is now displayed by the
VM.start_java_debugging command, if a new session was started.
webrev: http://cr.openjdk.java.net/~rschmelter/webrevs/8223065/webrev.0/
bugreport: https://bugs.openjdk.java.net/browse/JDK-8223065
Best regards,
Ralf
