Bug 10333 - Conditional breakpoints don't evaluate properly
Summary: Conditional breakpoints don't evaluate properly
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-02-15 17:44 UTC by Jeffrey Stedfast
Modified: 2013-02-19 14:29 UTC (History)
1 user (show)

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:

Description Jeffrey Stedfast 2013-02-15 17:44:03 UTC
A user on the forums reported:

"the exact expression is: message.Id == RequestId.GAME_MOVE Where RequestId is an enum, and message is a struct."

It might be that something strange is happening to enums in the evaluator...
Comment 1 Jeffrey Stedfast 2013-02-19 14:29:27 UTC
I'm going to guess that the reason this failed was because we didn't resolve types. I've fixed this in git, so this bug is probably fixed now.