Pavel S
05/26/2023, 5:13 PMZac Sweers
05/26/2023, 7:26 PMPavel S
05/27/2023, 10:16 AM./gradlew :sample:build --no-daemon -Dorg.gradle.debug=true -Pkotlin.compiler.execution.strategy=in-process
where sample
is the gradle module that uses my processor with ksp(project(…))
, then launch “Attach to Process” action (pic 1), then chose the only process there was (pic 2), the only thing that happened was that the execution resumed and in the debug console I saw
Connected to the target VM, address: pid 2296
Disconnected from the target VM, address: pid 2296
and no breakpoints were hitPavel S
05/27/2023, 10:57 AM-Dkotlin.daemon.jvm.options="-Xdebug,-Xrunjdwp:transport=dt_socket\,address=5005\,server=y\,suspend=n"
however I feel like I don’t understand at all where it should go: if it should be appended to the previous one, or if it should be appended to the previous one but without the --no-daemon
, no idea. Then tried to debug it with a custom debug configuration (pic 1), but nothing happens as a result, I’ve never even seen the KotlinCompilerDaemon
processNorbi
05/31/2023, 10:20 PMefemoney
06/03/2023, 11:24 AM./gradlew :sample:build --no-daemon -Dorg.gradle.debug=true -Pkotlin.compiler.execution.strategy=in-process
Then run the Debug config from IDEefemoney
06/03/2023, 11:27 AMEdit configurations
and adding a new jvm debug one. Leave the settings at default (and probably name it). Then after running the command in terminal, Debug this new configuration.efemoney
06/03/2023, 11:29 AMNorbi
06/03/2023, 1:36 PM