Rider remote debugging (remote process attach) breakpoints are not working, and module load failure issue
Hello,
I attempted to debug an Exchange Server running on a Windows Server using Rider’s Remote Debugging feature. However, for some reason, the modules are not being loaded, and even when I load the DLLs locally, breakpoints fail to trigger
What could be the reason for this?
Please sign in to leave a comment.
Hello,
The message "Symbols are not loaded yet" means you are missing .pdb files for debugging corresponding .dll.
Normally debugging (stepping through the code) a .dll requires .pdb. Rider provides no options to Debug a .dll/.exe having no .pdb for it.
Meantime, we have plans to implement this feature: RIDER-21114 Decompile external code during remote debug. We expect it will be possible to decompile the target .dll/.exe on the fly and step through the decompiled code. Unfortunately, I have no ETA to share.
Additional note: when this is implemented, it will only work for apps that are built on top of .NET.
Have a nice day!