Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attaching to remote debugger causes exception upon breakpoint #50

Open
timbob2000 opened this issue Aug 11, 2020 · 1 comment
Open

Attaching to remote debugger causes exception upon breakpoint #50

timbob2000 opened this issue Aug 11, 2020 · 1 comment

Comments

@timbob2000
Copy link

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

@fwcd fwcd transferred this issue from fwcd/vscode-kotlin Sep 20, 2020
@pF-luis
Copy link

pF-luis commented Jan 16, 2023

Are there any news to this, got the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants