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 24194 on
Developer Community or GitHub 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
@mjhutchinson mentioned this feature in his talk at evolve but it's not actually working.
=== Xamarin Studio ===
Version 5.6.2 (build 5)
Installation UUID: f5839db7-406e-4ff4-b8f7-94a64c07ad2b
Mono 3.10.0 ((detached/633e444)
GTK+ 2.24.23 (Raleigh theme)
Package version: 310000020
=== Apple Developer Tools ===
Xcode 6.1 (6604)
=== Xamarin.Mac ===
=== Xamarin.iOS ===
Version: 184.108.40.206 (Business Edition)
Build date: 2014-10-20 21:48:06-0400
=== Xamarin.Android ===
Version: 4.18.0 (Starter Edition)
Android SDK: /Users/skimania/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0.3 (API level 15)
4.4 (API level 19)
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)
=== Build Information ===
Release ID: 506020005
Git revision: 19bc3b64b70332bfab18faf9cf1ce7d3aa191b36
Build date: 2014-10-17 14:49:01-04
=== Operating System ===
Mac OS X 10.10.0
Darwin Erics-MacBook-Pro.local 14.0.0 Darwin Kernel Version 14.0.0
Fri Sep 19 00:26:44 PDT 2014
Marius: you implemented this feature, didn't you? or was it David?
Pretty sure it was David.
are you debugging Console application, Xamarin.Mac, Xamarin.iOS(simulator or device) or Xamarin.Android(simulator or device)?
As per Comment#3 changing the status to NEEDINFO.
Hey, i thought I responded to this already, but this is using the IOS Simulator and on device.
New Info: Whenever running code in Release Mode all output is Red.
Um, is there any update on this? Seems to make sense to make the output red in debug mode as well. I also tried to use this based on the suggestion by @mjhutchinson
FYI I am debugging a Xamarin.iOS application using the simulator. Xamarin Studio 5.7, OSX 10.10.2
Still happening with Xamarin Studio 6.2 for iOS projects and a C# console project.
I investigated this a bit, problem is that Xamarin.iOS is using NSLog() method to write anything that is written to Console.WriteLine or Console.Error, afaik reason for this is because it writes into device log + writing to fd=1(stdout) and fd=2(stderr) causes problems if device is not in developer mode...
So what will need to change for start https://github.com/mono/mono/blob/e1b885c/mcs/class/corlib/System/Console.cs#L146-L147 will need to pass true/false(error or output).
After that https://github.com/mono/mono/blob/4504107/mcs/class/corlib/System/Console.iOS.cs#L51 will need to pass this boolean down to native implementation `xamarin_log`. Which will then need some logic to decide to use NSLog or stdout/stderr to write messages...
When debugger is connected it would make most sense to decide based on https://github.com/xamarin/xamarin-macios/blob/ad3a4a1/runtime/monotouch-debug.m#L1255-L1258 if `connect stderr/stdout`(use stderr/stdout) instead of `connect output`(use NSLog)...
Similar logic should probably also be applies to fix Bug 20211.
Reassigning this to XI as changes are needed there.