Bug 44420 - [Papercut - Windows]Large Package Name Lengths cause Debugger to not attach and crash application
Summary: [Papercut - Windows]Large Package Name Lengths cause Debugger to not attach a...
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: General (show other bugs)
Version: 7.0 (C8)
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
: 52576 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-16 16:03 UTC by Jon Douglas [MSFT]
Modified: 2017-06-27 15:03 UTC (History)
3 users (show)

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


Attachments
logcat of VS Simulator (15.06 KB, text/plain)
2016-09-16 16:03 UTC, Jon Douglas [MSFT]
Details

Description Jon Douglas [MSFT] 2016-09-16 16:03:32 UTC
Created attachment 17545 [details]
logcat of VS Simulator

*Description:

It seems that there's a maximum package length that plays nicely with attaching the debugger. However if you exceed that maximum, the debugger has problems attaching. For example:

A) Aaaaaa.Bbbbbbbb.Cccccccc.Dddddddd.Aaaaaa.Bbbbbbbb.Cccccccc (58 characters)

B) Aaaaaa.Bbbbbbbb.Cccccccc.Dddddddd.Aaaaaa.Bbbbbbbb.Cccccccccccccccccccccccccccccccccc (84 characters)

In the first scenario A) the debugger attaches and all is well.

In the second scenario B) the debugger fails to attach and actually crashes the application.

I tested this on both a physical device and emulator:

Physical Device - Nexus 5 - 6.0.1

VS Emulator - 6.0

*Reproduction:

[Ensure you are on a Windows PC with the latest stable as defined in *Version below]

1) File -> New Blank Android Application

2) Change the Package Name inside Android Manifest options to A) and B) to see the differences

*Expected Behavior:

The debugger should attach and be able to resolve a simple breakpoint with a long package name. Or it should be validated on the Windows side to enforce any Windows policies.

*Version Information:

Microsoft Visual Studio Professional 2015
Version 14.0.25421.03 Update 3
Microsoft .NET Framework
Version 4.6.01038

Installed Version: Professional

Xamarin   4.2.0.680 (c4382f5)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   7.0.0.18 (0e59c36)
Visual Studio extension to enable development for Xamarin.Android.

Xamarin.iOS   10.0.0.6 (6c3fee4)
Visual Studio extension to enable development for Xamarin.iOS.
Comment 1 John Miller [MSFT] 2017-06-26 15:32:52 UTC
I was able to reproduce this issue with the following version:

Microsoft Visual Studio Enterprise 2017 
Version 15.2 (26430.12) Release
VisualStudio.15.Release/15.2.0+26430.12
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Enterprise

Xamarin   4.5.0.476 (1be4f0c)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android SDK   7.3.1.2 (9dbc4c5)
Xamarin.Android Reference Assemblies and MSBuild support.

Xamarin.iOS and Xamarin.Mac SDK   10.10.0.35 (4cffddf)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Comment 2 Tom Opgenorth 2017-06-27 15:03:27 UTC
*** Bug 52576 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.