Bug 44808 - Breakpoints don't hit with "Link framework SDKs Only" option enabled.
Summary: Breakpoints don't hit with "Link framework SDKs Only" option enabled.
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Other ()
Version: 2.10.0 (C8)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-09-28 06:00 UTC by Mikhail Rozhkov
Modified: 2017-04-27 16:28 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Sample screenshot of unreachable breakpoints (150.77 KB, image/png)
2016-09-28 06:00 UTC, Mikhail Rozhkov

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Mikhail Rozhkov 2016-09-28 06:00:32 UTC
Created attachment 17778 [details]
Sample screenshot of unreachable breakpoints

When I change Link behavior from "Don't link" to "Link framework SDKs Only" some breakpoints are marked as unreachable.
Comment 1 Chris Hamons 2016-09-28 13:29:51 UTC
When we link SDK, the linker does some tricks to dead code string. However, in this example I don't see why those couldn't get hit.

It could be a bug either in mcs, our linker, or the debugger.

Could you attach a small example showing the problem? Just a screenshot isn't enough to go on.
Comment 2 Timothy Risi 2017-04-27 16:28:27 UTC
We have not received the requested information. If you are still 
 experiencing this issue please provide all the requested information 
 and re-open the bug report. Thanks!