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.
When trying to set a condition like "foo == null" or "Object.ReferenceEquals (foo, null)", the debugger complains with "Failed to evaluate expression in conditional breakpoint. Expression not supported." which makes it impossible afaict to have a conditional breakpoint on a null value.
implemented in git master
We have checked this issue with following XS:
XS 4.2.3(Build 36)
For "Object.ReferenceEquals (foo, null)" conditional breakpoint, we are still getting same error "Failed to evaluate expression in conditional breakpoint. Expression not supported."
However, for "foo == null" conditional breakpoint, we are not getting any error on output window.
So, we are still getting same issue with "Object.ReferenceEquals (foo, null)" conditional breakpoint.
Hence, Reopening this issue.
Please, let us know if we have to check any thing else.
this should be fixed now in git master
We have checked this issue with latest build of XS:
XS 4.2.3(Build 53)
Release ID: 402030053
Build date: 2014-01-28 16:29:18Z
Xamarin addins: 9f6123a63fc5c8475e8951c9b6e573c01076bc22
We are still getting same behavior mentioned in Comment 2.
Please, let us know if this issue is fixed with any other build.
It's in master, so setting back to RESOLVED and changing milestone.
I have verified this and observed that for "Object.ReferenceEquals (foo, null)" conditional breakpoint hit.
Refer screen shot: http://screencast.com/t/Iivdji6jr
Xamarin Studio: 4.2.4 (build 14)
Release ID: 402040014
Git revision: d36f82139fd61a0cda68d5baabb1c7b8402116b9
Xamarin addins: 79a1e35d2f486ba15541d74724e764c81878ab16