- relates to
-
JDK-8159615 SA: attach_internal crashes
-
- Closed
-
-
JDK-6794892 sa-jdi tests fail with "Unable to deduce type of thread from address" on windows-x64 with server jvm
-
- Closed
-
-
JDK-7016268 Can't get strata information through SA-JDI
-
- Closed
-
-
JDK-7174275 nsk.sajdi tests fail on Solaris-sparc64 with exception: Can't create thread_db agent!
-
- Closed
-
-
JDK-8049957 nsk/sajdi/jdb/options/connect/connect002 fails with "Debuggee core file not found"
-
- Closed
-
-
JDK-8061717 Multiple SA-JDI tests fail on windows with "Unable to find pid of started process with jps in 30 tries"
-
- Closed
-
-
JDK-6339436 SA : field _s_vm_release not found exception thrown for linux core file.
-
- Closed
-
-
JDK-6784496 SA-JDI: ReferenceType.allFields doesn't return fields from all superclasses
-
- Closed
-
-
JDK-6784504 SA-JDI: ReferenceType.majorVersion throws ClassCastException for arrays
-
- Closed
-
-
JDK-6784510 SA-JDI: can't use ThreadReference.ownedMonitorsAndFrames()
-
- Closed
-
-
JDK-7016692 Error getting thread stack trace via SA-JDI on windows-amd64
-
- Closed
-
-
JDK-7016880 SA-JDI: RuntimeException: wrong type on stack (found: v expected: r)
-
- Closed
-
-
JDK-8054084 nsk/sajdi/ThreadReference/frame/frame002 fails with "ThreadReference.frameCount() returned too few frames for running threads"
-
- Closed
-
-
JDK-8052404 vm/mlvm/indy/func/sajdi/*OtherStratumInStackTrace fail with "Exception when getting stack trace"
-
- Closed
-
-
JDK-8153624 SA-JDI: Binder should control how long to wait for a connection to debugee
-
- Closed
-
-
JDK-6708995 SA: nsk sajdi test comptype001 fails: field.type() throws class not loaded exception.
-
- Closed
-
-
JDK-8153602 SA-JDI tests have a problem on Linux during nightly testing
-
- Closed
-
-
JDK-8158050 Remove SA-JDI
-
- Resolved
-
Remove SA-JDI from tests
The sajdi tests also need to be removed. See linked bug for removal of SA-JDI code.
(13 relates to)