Question
Rider ↔ Unity IL2CPP Debugger: Why do breakpoints sometimes fail to resolve?
Rahul Maple
0 reputation · 06 Dec 2022, 17:47 UTC
89.9K views0
Goal
Determine why Rider’s IL2CPP debugging setting does not consistently allow breakpoints in managed C# scripts to be hit when the Unity project targets the IL2CPP scripting backend.
Constraints & Uncertainty
• Rider 2024.x and Unity 2022.x LTS are the documented baseline.
• The setting Build, Execution, Deployment → Debugger → Enable IL2CPP debugging is intended to load generated .pdb files.
• Users report that breakpoints still miss even when the setting is enabled, suggesting an unresolved decision about default symbol handling across Unity versions.
Specific Questions
- Which exact path does Rider expect for the
.pdbfiles produced by an IL2CPP build, and does this path change between Unity releases? - When the setting is enabled, does Rider automatically detect and load the correct
.pdbfiles, or is manual intervention required? - Is there a recommended workflow or configuration that guarantees consistent breakpoint resolution for IL2CPP targets across different platforms?
unity