Bug 18371 - Incorrect Object not compatible with constrained type at 0x000a
Summary: Incorrect Object not compatible with constrained type at 0x000a
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: Verifier ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Rodrigo Kumpera
URL:
Depends on:
Blocks:
 
Reported: 2014-03-13 17:08 UTC by Marek Safar
Modified: 2014-08-07 07:24 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
test (3.50 KB, application/x-msdownload)
2014-03-13 17:09 UTC, Marek Safar
Details


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 GitHub or Developer Community 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:
Status:
RESOLVED FIXED

Description Marek Safar 2014-03-13 17:08:16 UTC
In method: FlagsAttributeDemo::Main()
Not Verifiable: Object not compatible with constrained type at 0x000a

<nothing> on .net
Comment 1 Marek Safar 2014-03-13 17:09:53 UTC
Created attachment 6309 [details]
test
Comment 2 Marek Safar 2014-05-29 06:54:30 UTC
Fixed in master
Comment 3 Saurabh 2014-08-06 09:38:10 UTC
Could you please provide some steps so that I can check this Issue at my end?
Comment 4 Marek Safar 2014-08-07 07:24:34 UTC
peverify <attachement>

should not produce any errors