Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
* Create a new project from a template.
* Select a device configuration.
* Add to the additional mtouch arguments: "--gcc_flags -all_load"
* Enable profiling.
> duplicate symbol _monoeg_g_array_new in:
> duplicate symbol _monoeg_g_array_sized_new in:
@Zoltan, can you have a look? This regressed here: https://github.com/mono/mono/commit/2b74940f64fb39b727b882c278eda31e06a15fcf
I have checked this issue with the help of steps given in bug description and able to reproduce the reported behaviour. Please refer the screencast : http://www.screencast.com/t/cAGymorUGwvJ
Build Output : https://gist.github.com/Udham1/0332e73e871982fcff16
Ide Log : https://gist.github.com/Udham1/9eb5b554509d57cb93b5
Environment Info :
=== Xamarin Studio ===
Version 5.9 (build 464)
Installation UUID: ce927b2a-2c07-44c5-b186-09cfdafba6dc
Mono 4.0.1 ((detached/5a0b19f)
GTK+ 2.24.23 (Raleigh theme)
Package version: 400010024
=== Apple Developer Tools ===
Xcode 6.2 (6776)
=== Xamarin.iOS ===
Version: 188.8.131.52 (Enterprise Edition)
Build date: 2015-05-04 17:01:32-0400
=== Xamarin.Android ===
Version: 184.108.40.206 (Enterprise Edition)
Android SDK: /Users/xamarin76/Desktop/android-sdk-macosx
Supported Android versions:
2.3 (API level 10)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
=== Xamarin Android Player ===
Version: Unknown version
Location: /Applications/Xamarin Android Player.app
=== Xamarin.Mac ===
Version: 220.127.116.11 (Enterprise Edition)
=== Build Information ===
Release ID: 509000464
Git revision: 97f3c43266a4abe2dff0a31b1afb976de897d099
Build date: 2015-05-04 10:06:54-04
Xamarin addins: 438f3e4b8352e006958552de07c6f54770c9233c
=== Operating System ===
Mac OS X 10.9.5
Darwin Xamarin76s-Mac-mini.local 13.4.0 Darwin Kernel Version 13.4.0
Sun Aug 17 19:50:11 PDT 2014
The problem is that the shared version of libmono-profiler-log needs to be linked eglib, but the static one doesn't, since it will be linked against libmono which already links against eglib.
Is there a workaround for this issue while we wait for a fix?
## Possible workarounds
A. Disable profiling under "Project Properties -> iOS Build".
B. If your app uses the `-all_load` linker flag (via either `gcc_flags`  or `LinkerFlags` ), try removing it.
>  http://developer.xamarin.com/guides/ios/advanced_topics/native_interop/
>  http://developer.xamarin.com/guides/ios/advanced_topics/binding_objective-c/binding_types_reference_guide/#LinkWithAttribute.LinkerFlags
(Copied from the forum release thread:
@rolf: This can be fixed by cherry-picking 51f42669b2db7c37cd413d195df07638e0048ef1 from master and using the attached patch to maccore.
That's maccore patch is fine.
I'll add that patch to maccore once we switch to mono/master (for C7 likely).
This can be backported to old versions if needed.
@Zoltan, ok, maybe I should try to get it into C6SR1. Can you backport to mono's mono-4.2.0-thawed branch?
Applied the maccore patch to maccore master f773a69bed449844a4e9ad3251efc0dddc77840f.
I am able to reproduce this issue with XS 18.104.22.168. However it is working fine with latest Master Builds i.e.
Here is the screencast for the same: http://www.screencast.com/t/1VslnCMP
*** Bug 36390 has been marked as a duplicate of this bug. ***