Bug 42486 - SIGSEGV while executing native code
Summary: SIGSEGV while executing native code
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 9.8 (tvOS / C7)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-07-12 10:32 UTC by Adam Hartley [MSFT]
Modified: 2016-08-04 09:30 UTC (History)
7 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 NORESPONSE

Description Adam Hartley [MSFT] 2016-07-12 10:32:59 UTC
## Steps to reproduce

Build and run app on a device - during my testing it appeared to be crashing on 32-bit devices only (see XTC link in next comment)

## Expected result

App should not crash

## Actual result

App crashes on 32-bit devices

## Notes

Customer is building with Mono 4.2 and appears to have the app crash on iPhone 4s (9.1) and iPhone 6s (9.0.2). During my own testing, I built the app with Mono 4.4.2 and the app ran fine on iPhone 6s devices (and all other 64-bit devices)
Comment 2 Adam Hartley [MSFT] 2016-07-12 10:35:16 UTC
Version info:

=== Xamarin Studio Enterprise ===

Version 6.0.1 (build 9)
Installation UUID: ad66a985-3d32-4bb5-935b-a2e10c4f0de0
Runtime:
	Mono 4.4.1 (mono-4.4.0-branch-c7sr0/4747417) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404010000

=== Xamarin.Profiler ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.3.1 (10188.1)
Build 7D1014

=== Xamarin.iOS ===

Version: 9.8.1.4 (Visual Studio Enterprise)
Hash: 3cf8aae
Branch: c7sr0
Build date: 2016-06-20 16:09:58-0400

=== Xamarin.Android ===

Version: 6.1.1.1 (Visual Studio Enterprise)
Android SDK: /Users/Adam/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		6.0 (API level 23)

SDK Tools Version: 25.1.2
SDK Platform Tools Version: 24.0.0
SDK Build Tools Version: 23.0.2

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin Android Player ===

Not Installed

=== Xamarin.Mac ===

Version: 2.8.1.4 (Visual Studio Enterprise)

=== Build Information ===

Release ID: 600010009
Git revision: e879ce52093257c5c386ad7e390dfaa937fa7f90
Build date: 2016-06-24 11:53:43-04
Xamarin addins: a9252e6df4851fbbed1f9c6228e7b6dd1b475ac5
Build lane: monodevelop-lion-cycle7-sr0

=== Operating System ===

Mac OS X 10.11.5
Darwin Adams-MacBook-Pro.local 15.5.0 Darwin Kernel Version 15.5.0
    Tue Apr 19 18:36:36 PDT 2016
    root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
Comment 6 Adam Hartley [MSFT] 2016-07-12 11:09:09 UTC
Customer updated to Mono 4.4 and it appears to now work on iPhone 6s devices - awaiting feedback for 4s / 32-bit.
Comment 7 Manuel de la Peña [MSFT] 2016-07-14 09:24:48 UTC
Setting the bug to need info until we get the info about the other devices.
Comment 12 Manuel de la Peña [MSFT] 2016-08-04 09:30:21 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!