Hi how do i attach a debugger to the kotlin compilation proc

Question

Hi how do i attach a debugger to the kotlin compilation process to look into a compiler plugin Attaching to the gradle process does not seem to do the trick it hits my gradle plugin but the kotlin plugin doesn t hit but it is being invoked

Nick Chong · Answer

replying to this thread as I am also curious bout this

dmitriy.novozhilov · Answer

You can run the kotlin daemon with opened debug port using this spell ``` gradlew Dkotlin daemon jvm options= agentlib jdwp=transport=dt socket server=n suspend=n address=5005 taskToRun``` And to attach debugger you need to create and start the following run configuration int the IDE

Justin Tullgren · Answer

do i need to start the gradle process in debug mode too

dmitriy.novozhilov · Answer

Note that this setup implies that debugger is the server and kotlin daemon process is a client so you need to start debugger before running the compilation If you want switch them you can change `server=n` to `server=y` in the spell and change debugger mode in the configuration to Attach to remote JVM

dmitriy.novozhilov · Answer

gt do i need to start the gradle process in debug mode too No you don t

Justin Tullgren · Answer

ok i l try it out thanks

dmitriy.novozhilov · Answer

Also I prefer to restart the daemon after restarting debugging session so usually I use this bash zsh alias in everyday work ```alias gdwDebugS= gradlew stop amp amp gradlew Dkotlin daemon jvm options= agentlib jdwp=transport=dt socket server=n suspend=n address=5005 ```

Justin Tullgren · Answer

should i just use no daemon

dmitriy.novozhilov · Answer

Yes this way can be used to In this case you need to disable kotlin daemon with some gradle property I don t remember which one exactly sorry and then just run gradle itself in debugger mode AFAIK it opens the 5005 port so you need to use same configuration in Attach to remote JVM mode

Justin Tullgren · Answer

ok thanks i m setting it up to give it a go i ll reach back out if i can t figure it out thanks so much

Justin Tullgren · Answer

Unfortunately it doesn t seem to work

Justin Tullgren · Answer

Screenshot 2023 09 21 at 07 09 25 png Screenshot 2023 09 21 at 07 09 44 png

dmitriy.novozhilov · Answer

Did you try to remove ` no daemon`

Justin Tullgren · Answer

yes

Justin Tullgren · Answer

and tried attaching to vm switching the cli call to server=y

dmitriy.novozhilov · Answer

There are two daemons gradle daemon and kotlin daemon and I m not sure how it works if you disable the first one but not the second

dmitriy.novozhilov · Answer

Try `server=y` and `suspend=y` In this case kotlin daemon should suspend until you attach the debugger or fail one minute later and fallback to no daemon mode

Justin Tullgren · Answer

k trying

dmitriy.novozhilov · Answer

If IDE shows that debugger attached successfully try to press pause button to check if it really works

Justin Tullgren · Answer

``` gradlew Dkotlin daemon jvm options= agentlib jdwp=transport=dt socket server=y suspend=y address=5005 thunderhead apps app compose ui clean thunderhead apps app compose ui build ```

Justin Tullgren · Answer

didn t pause

Justin Tullgren · Answer

just ran through

dmitriy.novozhilov · Answer

Did you kill daemons first with ` gradlew stop`

Justin Tullgren · Answer

i ll do it again and make sure

wasyl · Answer

I recently had success with debugging a Gradle task directly from IJ with setting `kotlin compiler execution strategy=in process` in `gradle properties` and running the Gradle task from IJ with shift pressed it switches to debugging `execute gradle task` action type task shift + enter I was able to successfully stop in an Anvil plugin this way

dmitriy.novozhilov · Answer

< wasyl> that was the flag I mentioned before thank you

Justin Tullgren · Answer

k i ll give that a go

Justin Tullgren · Answer

that did it with the remote server debug

Justin Tullgren · Answer

thank you both