Do not shadow ByteBuddy agent

This way, it can work even with BlockHound on JDK8, which also uses
ByteBuddy and thus was in conflict.

Kind of solves
#1060, but since
now the debugging routine depends on BlockHound, where, it seems,
the same problem was not fixed, the original cause for concern
probably still stands.

Author: dkhalanskyjb

gradle.properties

@@ -13,7 +13,7 @@ atomicfu_version=0.14.1
 html_version=0.6.8
 lincheck_version=2.5.3
 dokka_version=0.9.16-rdev-2-mpp-hacks
-byte_buddy_version=1.9.3
+byte_buddy_version=1.10.7
 reactor_vesion=3.2.5.RELEASE
 reactive_streams_version=1.0.2
 rxjava2_version=2.2.8

kotlinx-coroutines-debug/build.gradle

@@ -21,9 +21,10 @@ configurations {
 dependencies {
     compileOnly "junit:junit:$junit_version"
     shadowDeps "net.bytebuddy:byte-buddy:$byte_buddy_version"
-    shadowDeps "net.bytebuddy:byte-buddy-agent:$byte_buddy_version"
+    compile "net.bytebuddy:byte-buddy-agent:$byte_buddy_version"
     compile 'io.projectreactor.tools:blockhound:1.0.1.BUILD-SNAPSHOT'
     compile "org.jetbrains.kotlin:kotlin-reflect:$kotlin_version"
+    runtime "net.java.dev.jna:jna:5.5.0"
 }
 
 jar {

kotlinx-coroutines-debug/src/internal/DebugProbesImpl.kt

@@ -47,7 +47,7 @@ internal object DebugProbesImpl {
     public fun install() {
         if (++installations > 1) return
 
-        ByteBuddyAgent.install()
+        ByteBuddyAgent.install(ByteBuddyAgent.AttachmentProvider.ForEmulatedAttachment.INSTANCE)
         val cl = Class.forName("kotlin.coroutines.jvm.internal.DebugProbesKt")
         val cl2 = Class.forName("kotlinx.coroutines.debug.DebugProbesKt")