Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
If you run the application, stop somewhere at the breakpoint and then forcefully exit via "Stop" command, you end up with the locked executable. Any consequent attempts to rebuild the project fails because MSBuild can't overwrite the occupied pdb file. I've attached a demo video.
Created attachment 6788 [details]
I have tried to reproduce this issue with following builds:
X.S 4.2.5(Build 0)
Git revision: 95ac543f224a70960a9ab71e24ce341eb87de06f
In my case when I click on 'Stop' button somewhere at the breakpoint, debugger gets disconnected and application gets stopped. This is the screencast for the same: http://www.screencast.com/t/Wjhbo7xJeMWy
@Lopatkin, Could you please let me know which SamarinStudio build you are using?
No, in fact it's not the same sequence of actions. I'm sorry, I've used shortcut (Control+F8) for rebuild and thought that it will be clear that I did it. In your scenario you've just rerun the same executable with attached debugger what doesn't requre write access to .exe or .pdb file. The key point here is to rebuild it. Like you've debugged the problem, fixed it, and now want to run debugger again with the fresh code compiled.
I belive that the specific build is not important because I've been observing this bug for a couple of years. Estimately from the MonoDevelop 3.0 times.
Could you please check the rebuild scenario?
Most cases when .pdb would be locked and require restart is now resolved in master. Before this change I had to restart XS every few hours now it only happened only once in 2 weeks.(Still have to find reason and fix this case)... After this case is fixed and if I won't get any locks for 1 month...
I will put this bug on resolved... So with next version(probably 5.1) of XS you shouldn't have problems with this anymore...
*** Bug 20284 has been marked as a duplicate of this bug. ***
I've updated to the current trunk version and now it's broken again. Every 2-3 debug sessions XS locks my files though before update everything worked more or less fine.
I'm currently seeing this pretty much every time I debug XS with XS.
I assume this is in the CorDebugger backend?
might be duplicated with Bug 26841
To add a few more keywords to this bug report for searchability, here's the warning message transcribed from the "View -> Pads -> Errors" window in the video from comment 0 (and translated to English thanks to bug 20284):
> Could not copy "obj\x86\Debug\Test.pdb" to "bin\Debug\Test.pdb". Beginning
> retry 1 in 1000ms. The process cannot access the file 'bin\Debug\Test.pdb'
> because it is being used by another process. (MSB3026)
Fixed in version 220.127.116.114 (new-project-model)
Not yet fixed.
Fixed in version 18.104.22.1686 (roslyn)
*** Bug 29186 has been marked as a duplicate of this bug. ***
This was fixed with release of XS 6.0
*** Bug 9951 has been marked as a duplicate of this bug. ***