Bug 41725 - PEVerifier failing for osx mono:latest
Summary: PEVerifier failing for osx mono:latest
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: Verifier ()
Version: 4.4.0 (C7)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Rodrigo Kumpera
URL:
Depends on:
Blocks:
 
Reported: 2016-06-10 22:19 UTC by test2
Modified: 2016-07-21 05:39 UTC (History)
2 users (show)

Tags:
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 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 test2 2016-06-10 22:19:43 UTC
PEVerifier failing on various assemblies for osx mono:latest (but linux mono:latest is fine, osx mono 4.2.2 is fine):

PEVerifier.Verify (System.String assemblyPath) <0x6e9c6c0 + 0x00337>
Verification of 'some_assembly_path' failed with code 134, message <<<* Assertion at ../../mono/utils/mono-os-mutex.h:71, conditionres != EINVAL' not met >>>

Source here: https://travis-ci.org/fsharp/FSharp.Compiler.Service/jobs/136778483
Comment 1 test2 2016-06-10 22:28:15 UTC
Problem started appearing after June 9th 2016, it was fine before that.
Comment 2 Rodrigo Kumpera 2016-06-10 23:52:32 UTC
Just tested with mono 4.5.1 and it's working as expected.
Comment 3 test2 2016-06-11 17:41:54 UTC
Sorry, I probably misclasified the bug under 4.5x when it was actually 4.4.0.0
Here is the version info from Travis CI (see the link above).

mono --version

Mono JIT compiler version 4.4.0 (mono-4.4.0-branch-c7-baseline/5995f74 Thu Jun  2 15:13:10 EDT 2016)

Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com

	TLS:           normal

	SIGSEGV:       altstack

	Notification:  kqueue

	Architecture:  x86

	Disabled:      none

	Misc:          softdebug 

	LLVM:          yes(3.6.0svn-mono-master/a173357)

	GC:            sgen
Comment 4 Rodrigo Kumpera 2016-07-21 05:39:02 UTC
Fixed in 4.6.0