Comment by thaumasiotes
11 hours ago
> So I fixed the debugger (it turned out to be a one-line configuration change)
That line links to the commit, which adds
.withDebug(true)
to an invocation of GradleRunner in a file named AllFunctionalTests.kt in the krossover project.
My question is:
Why can the software choose whether, when I run a debugger on it, the debugger will work?
It can't, of course, so what's going on?
I also clicked through to that and was similarly confused. Not a Kotlin dev but this doesn’t really seem like fixing your tools? More like understanding them properly. I wouldn’t call a configuration change like this “debugging the debugger” as another comment mentioned.
I’d also like to know the answer to your question about what is going on. I know Java and maven but not kotlin or gradle, but wouldn’t a debugger be interfacing more at the JVM level?
yea, good point. The debugger should be able to say up front. "This code isn't debuggable" or some warning to that effect.