fwcd / fwcd/kotlin-debug-adapter
Attaching to remote debugger causes exception upon breakpoint
- Dominant language
- Kotlin
- Stars
- 150
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Please file the issue here: https://github.com/fwcd/kotlin-debug-adapter/issues
Description:
When using the remote debugger, attaching to an existing gradle run task, an exception ocurres when attempting to stop on a breakpoint.
./gradlew run --debug-jvm
and the following launch config:
{
"type": "kotlin",
"hostName": "localhost",
"port": 5005,
"timeout": 30000,
"request": "attach",
"name": "Attach to remote debugger",
"projectRoot": "${workspaceFolder}",
}
Exception:
Caused by: com.sun.jdi.AbsentInformationException
at jdk.jdi/com.sun.tools.jdi.StratumLineInfo.liSourcePath(StratumLineInfo.java:61)
at jdk.jdi/com.sun.tools.jdi.LocationImpl.sourcePath(LocationImpl.java:201)
at jdk.jdi/com.sun.tools.jdi.LocationImpl.sourcePath(LocationImpl.java:191)
at org.javacs.ktda.jdi.JDIDebuggee.sourceOf(JDIDebuggee.kt:167)
at org.javacs.ktda.jdi.JDIDebuggee.positionOf(JDIDebuggee.kt:163)
at org.javacs.ktda.jdi.stack.JDIStackFrame.(JDIStackFrame.kt:19)
at org.javacs.ktda.jdi.stack.JDIStackTrace.(JDIStackTrace.kt:11)
at org.javacs.ktda.jdi.JDIThread.stackTrace(JDIThread.kt:35)
at org.javacs.ktda.jdi.JDIThread.stackTrace(JDIThread.kt:14)
at org.javacs.ktda.adapter.KotlinDebugAdapter.stackTrace(KotlinDebugAdapter.kt:341)
... 16 more
JDK: Open JDK 11
Kotlin Version: 1.3.70
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the failure with ./gradlew run --debug-jvm and the shown attach configuration on OpenJDK 11. Start in org.javacs.ktda.jdi.JDIDebuggee.sourceOf and positionOf, then inspect JDIStackFrame and JDIStackTrace where the breakpoint stop triggers AbsentInformationException. Done means attaching and stopping at a breakpoint no longer produces this exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100