Bug 29609 - Seeing a SIGABRT on Nexus 9 when debugging using MONO_DEBUG=soft-breakpoints
Summary: Seeing a SIGABRT on Nexus 9 when debugging using MONO_DEBUG=soft-breakpoints
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 5.1
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: 6.0 (C6)
Assignee: João Matos
URL:
Depends on:
Blocks:
 
Reported: 2015-04-30 12:22 UTC by Peter Collins
Modified: 2015-06-04 15:38 UTC (History)
3 users (show)

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

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:
Status:
RESOLVED FIXED

Description Peter Collins 2015-04-30 12:22:24 UTC
I'm able to reproduce this when attempting to start debugging from both VS and XS on a Nexus 9. If I set MONO_DEBUG=soft-breakpoints in an AndroidEnvironment file I see the crash shown in the logcat output below. This is working on non 64-bit devices.

Logcat output:
https://gist.github.com/pjcollins/c7a2e174a4e76d6be7fb

Steps to reproduce:
1. Open or create a new Android app.
2. Add a 'plain text' file to the project, with the following text:
>    MONO_DEBUG=soft-breakpoints
3. Set the build action of this file to AndroidEnvironment.
4. Start debugging.

Environment:
Both Windows and Mac
XA 5.1-series / d23da369e (current stable)
Comment 1 Atin 2015-04-30 14:19:10 UTC
I have checked this issue and able to reproduce the above behavior with the help of steps given in the bug description.I checked this issue on Nexus 9(Api 21).

Screencast: http://www.screencast.com/t/nxbVrBhh
Device Logs: https://gist.github.com/saurabh360/3944c44e8d8585a1d67f
Ide Logs: https://gist.github.com/saurabh360/07d922fce68cb93e7671
Build Output: https://gist.github.com/saurabh360/6d7cfaf6255a82d6d853
Application Output: https://gist.github.com/saurabh360/518ab63ce9f13a30eeca

Environment Info:

=== Xamarin Studio ===

Version 5.9 (build 456)
Installation UUID: 642986ef-b668-4108-b6e5-f58c62d668b6
Runtime:
	Mono 4.0.0 ((detached/1aa57ef)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400000146

=== Apple Developer Tools ===

Xcode 6.3 (7569)
Build 6D570

=== Xamarin.iOS ===

Version: 8.10.0.267 (Enterprise Edition)
Hash: 6481535
Branch: master
Build date: 2015-04-27 04:38:13-0400

=== Xamarin.Android ===

Version: 5.1.0.122 (Enterprise Edition)
Android SDK: /Users/360logica/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: 2.0.1.0 (Enterprise Edition)

=== Build Information ===

Release ID: 509000456
Git revision: 2666387bc794c06828a59aa95d2435714f732b12
Build date: 2015-04-29 08:16:42-04
Xamarin addins: df9b5918c9f7aca6da509fe3e5a62553aa101910

=== Operating System ===

Mac OS X 10.10.0
Darwin 360Logicas-MacBook-Pro.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 2 Jonathan Pryor 2015-04-30 15:55:59 UTC
This is due to a runtime assert.

> F/        (27383): * Assertion: should not be reached at /Users/builder/data/lanes/monodroid-mavericks-monodroid-5.1-series/d23da369/source/mono/mono/mini/../../../mono-extensions/mono/mini/mini-arm64.c:4629
Comment 3 Zoltan Varga 2015-06-04 15:38:44 UTC
Soft-breakpoints are now the default on arm64, so this is no longer an issue.