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 for Bug 45993 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The process handling code (processes.c) is fairly big:
> > ls -laSh xamarin-macios/builds/*/*/*/processes.o
> -rw-r--r-- 1 rolf wheel 275K Oct 27 08:43 xamarin-macios/builds/targettv/mono/io-layer/processes.o
> -rw-r--r-- 1 rolf wheel 262K Oct 27 08:43 xamarin-macios/builds/targetwatch/mono/io-layer/processes.o
> -rw-r--r-- 1 rolf wheel 156K Oct 27 08:38 xamarin-macios/builds/target64/mono/io-layer/processes.o
> -rw-r--r-- 1 rolf wheel 142K Oct 27 08:37 xamarin-macios/builds/target7s/mono/io-layer/processes.o
> -rw-r--r-- 1 rolf wheel 142K Oct 27 08:24 xamarin-macios/builds/target7/mono/io-layer/processes.o
Much of this is not needed for iOS/tvOS/watchOS, so it should be possible to not build/include it at all by disabling it with configure flags.
Most of that is only accessed from icalls so it will be linked out.
It will only be linked out when linking with the static libmonosgen-2.0.a library, not when using the dynamic libmonosgen-2.0.dylib (which we currently ship as Mono.framework/Mono).