4 ms·
> 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 invocati
by thaumasiotes 8mo 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?
- socalgal2 8mo agoyea, good point. The debugger should be able to say up front. "This code isn't debuggable" or some warning to that effect.
- wisemang 8mo agoI 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?
- rileymichael 8mo agothe tests are validating the plugin by executing actual builds in an isolated/temporary gradle project. debugging doesn't work out of the box because it's another process https://docs.gradle.org/current/userguide/test_kit.html#sub:test-kit-debug https://docs.gradle.org/current/userguide/test_kit.html#sub:...