Bug 15628 - SIGSEGV in C++ code when running on iOS 7.0.3
Summary: SIGSEGV in C++ code when running on iOS 7.0.3
Status: RESOLVED DUPLICATE of bug 15506
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 7.0.0.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-10-23 13:50 UTC by Frank A. Krueger
Modified: 2013-10-23 14:04 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 DUPLICATE of bug 15506

Description Frank A. Krueger 2013-10-23 13:50:13 UTC
Compiling with MonoTouch 7.0.3 and running on iOS 7.0.3

If I compile and run with Debug builds, everything is fine.

If I switch to Release builds, then I get this crash when opening files.


Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: Stacktrace:
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 
	Native stacktrace:
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	0   Calca                               0x004d9d47 _ZNSt3__16__treeINS_4pairINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS_3mapIS7_iNS_4lessIS7_EENS5_INS1_IKS7_iEEEEEEEENS_19__map_value_compareIS7_SE_SA_Lb1EEENS5_ISF_EEE16__insert_node_atEPNS_16__tree_node_baseIPvEERSN_SN_ + 4199266
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	1   Calca                               0x004e48b1 _ZNSt3__16__treeINS_4pairINS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEENS_3mapIS7_iNS_4lessIS7_EENS5_INS1_IKS7_iEEEEEEEENS_19__map_value_compareIS7_SE_SA_Lb1EEENS5_ISF_EEE16__insert_node_atEPNS_16__tree_node_baseIPvEERSN_SN_ + 4243148
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	2   libsystem_platform.dylib            0x39364723 _sigtramp + 42
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	3   libsystem_blocks.dylib              0x39268ac5 _Block_release + 216
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	4   libsystem_blocks.dylib              0x39268ac5 _Block_release + 216
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	5   libdispatch.dylib                   0x3923be7b <redacted> + 374
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	6   libdispatch.dylib                   0x39238f93 <redacted> + 42
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	7   libdispatch.dylib                   0x3923c745 <redacted> + 76
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	8   libdispatch.dylib                   0x3923c9c5 <redacted> + 56
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	9   libsystem_pthread.dylib             0x39366dff _pthread_wqthread + 298
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 	10  libsystem_pthread.dylib             0x39366cc4 start_wqthread + 8
Oct 23 10:43:37 Precious-XIII Calca[341] <Error>: 
	=================================================================
	Got a SIGSEGV while executing native code. This usually indicates
	a fatal error in the mono runtime or one of the native libraries 
	used by your application.
	=================================================================
Comment 1 Frank A. Krueger 2013-10-23 13:52:23 UTC
I should mention that that is the whole error from the Console. No crash report is generated.
Comment 2 Sebastien Pouliot 2013-10-23 14:04:20 UTC
That's fixed in an upcoming alpha build.

*** This bug has been marked as a duplicate of bug 15506 ***