Bug 59293 - Frame does not match source
Summary: Frame does not match source
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-09-07 14:50 UTC by Chris King
Modified: 2017-09-20 18:35 UTC (History)
8 users (show)

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


Attachments
Linker Test (2.19 MB, application/x-zip-compressed)
2017-09-11 17:52 UTC, Chris King
Details


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 for Bug 59293 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Chris King 2017-09-07 14:50:04 UTC
Expect frame to match source but actually doesn't. Possibly caused by mixing in Java frames. 

For reproduction steps, see

https://github.com/xamarin/Xamarin.Forms/blob/a462d0fcc8eef25d7908cd0b311e3140b9156572/Xamarin.Forms.Controls.Issues/Xamarin.Forms.Controls.Issues.Shared/Bugzilla52487.cs#L18

For minimum environment setup, used Parallels with clean Windows 10 + VS 2015 + Forms. See

  http://www.youtube.com/watch?v=jiQXOUAbYLI
  https://www.screencast.com/t/CkzSSLXI (with pauses)
 
For reproduction video, see (video doesn't show it but also repros with linker off)

  http://www.youtube.com/watch?v=Z4jQks-s-yE
  https://www.screencast.com/t/g6vrPU1o (with pauses)

Also verified reproduction using

  https://bosstoragemirror.blob.core.windows.net/wrench/monodroid-mavericks-d15-4/a5/a54187cd483a43b212005fa64acdc69d1e70e58e/Xamarin.Android.Sdk.8.0.0.3.vsix

Notes can be found in slack channel #qa-droid-dbg-vs2015
Comment 1 Chris King 2017-09-08 16:33:41 UTC
Use Xamarin.Forms branch debugger59347
https://github.com/xamarin/Xamarin.Forms/tree/debugger59347
Comment 2 Radek Doulik 2017-09-11 15:12:05 UTC
Could you try to build the project from command line with __XA_LOG_ERRORS__ set to icanhaz, like (part of monodroid's README.md):

> Further logging can be enabled by setting the `__XA_LOG_ERRORS__` environment
> variable to the value "icanhaz":
>
>         > set __XA_LOG_ERRORS__=icanhaz
>         $ export __XA_LOG_ERRORS__=icanhaz

and then attach the build diagnostic output here?

I am looking for lines printed by linker, starting with "Added method:".

If there are no such lines, then we can be sure, that it shouldn't be linker related.
Comment 3 Chris King 2017-09-11 17:52:24 UTC
Created attachment 24685 [details]
Linker Test

> set __XA_LOG_ERRORS__=icanhaz

> Xamarin.Forms.ControlGallery.Android>msbuild /v:m /flp:Verbosity=diag;LogFile=diag.log /t:rebuild

Contains no string: "Added method:"