Rider 2025.2 - Attach to an Unstarted Process Not Enabling Breakpoints
When my app is running and I attached to it, breakpoints are enabled and they hit. When I try Attach to an Unstarted Process, provide the process name and click Attach with LLDB, then start my app, Rider breaks at a point in assembly code and my .Net Core breakpoints are not enabled. They are still identified in Rider, just not enabled.
I clicked Run hoping my breakpoint would hit, but it does not. My breakpoints are in the execution path. I know this because when I use VS 2022 and Shift+Alt+P, the IDE attaches much faster than Rider and my first breakpoint is hit. I even tried putting a Thread.Sleep(10000) to try to give Rider more time, but then I realized that would never help since Rider is attaching, but all my breakpoints are disabled.
I left VS behind long ago. I really would like this to work in Rider. Any ideas? Thanks in advance for any help!
Please sign in to leave a comment.
Of course I had to try one more time… This time I used Shift+Alt+P (quickly), and a very late breakpoint, and it hit. I will try putting the sleep back in to see if I can hit a breakpoint closer to the beginning.
I'm surprised that VS attaches much faster than Rider.
Chris Vance "Attach to an Unstarted Process" feature is currently only available for the C++ projects. If you want to see this feature implemented for C#, please consider filing a feature request on our tracker: https://youtrack.jetbrains.com/issues/RIDER (New Issue→ Type: Feature). Please describe your use case in the issue description.
Well, that explains it! Thanks and I did add a new feature request.