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.
Breakpoint is still hit even after removing it
(Tested with master branch of MonoDevelop as of today)
I made a screencast: http://youtu.be/aCtuFpVwqAw
Can you still reproduce this? I haven't been able to.
Oh, I still do reproduce it, but just found out it only happens when my solution is inside a folder which is a symlink to other folder, like it happened in bug 5225, so I'm wondering if there are more path comparisons that are taking place without calling realpath() like we did in https://github.com/mono/monodevelop/commit/4346021d5754082b04cf961b79ed18c2f1946c82 ?
ah, yes, that could be...
okay, this *should* be fixed now
Thanks Jeff. To be honest I tried a very similar fix you did locally and didn't work, kept me thinking... then saw your fix, updated my MD and tested, didn't work either.
Then I thought of going back to basics again, I tested an even more basic test than the one in the screencast in comment#0, and it seems there is still some bug around this area which is not related to removing breakpoints but just about hitting them (again similar as bug 5225).
So I just opened a new bug, hopefully by fixing this one now everything will be ok?? The bug is 11092.