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 I add a function breakpoint on:
Then it gets resolved to the zero-argument version only:
However I would expect it to be resolved to all overloads unless I explicitly specify the zero-argument version using "System.Console.WriteLine()".
It would be nice if, after a function breakpoint resolved to multiple, the breakpoints pad made the breakpoint "expandable" to show individual overloads, so they could be enabled or disabled. IIRC VS does this.
All but the UI (breakpoint pad) functionality has now been implemented in git
Fixed in version 220.127.116.118 (a11y)
Author: Jeffrey Stedfast
Commit: 282c26a579a95969807ff42ea7f5dd97125e2235 (mono/debugger-libs)
Included in Commit: 815ccb4069c0e92b8db7231e8090f18556ea4e61 (mono/monodevelop)