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
GitHub or Developer Community 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.
public static void Main ()
var userAgent = "Mozilla/5.0 (iPhone; CPU iPhone OS 7_0 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Mobile/11A465";
var client = new HttpClient();
Doing a step over from the last line of the DefaultRequestHeaders accessor skips over the UserAgent and ParseAdd calls.
So we don't stop in the the end of the get_DefaultRequestHeaders method because it only has one seq point:
<method token="0x6000014" signature="System.Net.Http.Headers.HttpRequestHeaders System.Net.Http.HttpClient::get_DefaultRequestHeaders()">
<entry il="0x0" row="76" col="5" file_ref="7" />
and we don't stop before the UserAgent call, because the IL stack is not empty, and we don't stop there doing step overs, so we can step over nested calls.
This looks like a compiler bug, Marek?
It's not compiler bug. You need to build mono with --disable-bcl-opt to have precise sequence points but even with that it still does not work.
How come? It's missing a seqpoint at a non obvious place. How could sdb figure out where to stop?
It's not missing anything if you compile BCL with debugging support (otherwise there is no sequence point at closing "}" but that's expected).
This works now.