```> Task :redacted:kspKotlin FAILED
e: [ksp] U...
# kspj
JP Sugarbroad
09/26/2025, 11:57 PM Copy code
> Task :redacted:kspKotlin FAILED
e: [ksp] Unknown error processing element
e: [ksp] io.micronaut.inject.processing.ProcessingExceptionm
mbonnin
09/27/2025, 12:32 AMKSP1 had a line + column number but this is not released yet for KSP2
mbonnin
09/27/2025, 12:33 AMYou can also set a breakpoint: https://github.com/google/ksp/issues/31
j
JP Sugarbroad
09/27/2025, 12:45 AMYeah I found some instructions on how to attach a debugger and set a breakpoint
JP Sugarbroad
09/29/2025, 6:39 PMBut having a way to print the stack trace would help a lot
m
mbonnin
09/29/2025, 6:41 PMDon't you have that in the debugger?
j
JP Sugarbroad
09/29/2025, 6:41 PMWithout a debugger
JP Sugarbroad
09/29/2025, 6:41 PMksp1 printed the stack trace for exceptions, ksp2 does not
m
mbonnin
09/29/2025, 6:45 PMReally? What if you have multiple errors in the same KSP run? It would display a stacktrace for each?
j
JP Sugarbroad
09/29/2025, 6:45 PMIIRC yes
JP Sugarbroad
09/29/2025, 6:45 PMbut in this case I would just want a parameter to turn them on, not necessarily auto-print
m
mbonnin
09/29/2025, 6:45 PMThis sounds super verbose and not very useful for the average user that wants to fix their code (and not fix the processor)
mbonnin
09/29/2025, 6:46 PMI'd be OK with the parameter