Bug 40851 - Strong naming -> FieldAccessException
Summary: Strong naming -> FieldAccessException
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: JIT (show other bugs)
Version: 4.2.0 (C6)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-05-04 08:54 UTC by henrik
Modified: 2016-05-17 07:35 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 for Bug 40851 on GitHub or Developer Community 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 original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description henrik 2016-05-04 08:54:37 UTC
Strong naming of F# assemblies fails to run.

#### Repro steps

Try to run Hopac in a strongly named fashion.

1. Compile https://github.com/Hopac/Hopac/commit/bb2be0e1a12552ccb036e071d1a24748aaad5191
2. Try to run Tests/AdHocTests (or an example)
3. Crash with "FieldAccessException"

#### Expected behavior

It should run without a crash.

#### Actual behavior

Testing with the Cell example.
```
✗ mono --debug bin/Debug/Cell.exe
HopacReq:
Unhandled Exception:
System.FieldAccessException: Field `Hopac.Scheduler:TopLevelHandler' is inaccessible from method `Hopac.Platform.Scheduler:create (bool,Hopac.Job`1<int>,int,int,Microsoft.FSharp.Core.FSharpFunc`2<System.Exception, Hopac.Job`1<Microsoft.FSharp.Core.Unit>>)'

  at <StartupCode$Hopac-Platform>.$Init+Do@38.Invoke (Boolean arg1, Hopac.Job`1 arg2, Int32 arg3, Int32 arg4, Microsoft.FSharp.Core.FSharpFunc`2 arg5) [0x00000] in /Users/h/dev/haf/Hopac/Libs/Hopac.Platform.Net/Init.fs:38
  at Hopac.Scheduler.create (Hopac.Create c) [0x00075] in /Users/h/dev/haf/Hopac/Libs/Hopac/Hopac.fs:736
  at Hopac.Global.reallyInitGlobalScheduler () [0x00065] in /Users/h/dev/haf/Hopac/Libs/Hopac/Hopac.fs:835
  at Hopac.Job+Global.run[x] (Hopac.Job`1 xJ) [0x00000] in /Users/h/dev/haf/Hopac/Libs/Hopac/Hopac.fs:909
  at Cell+HopacReq.run (Int32 nCells, Int32 nJobs, Int32 nUpdates) [0x00025] in /Users/h/dev/haf/Hopac/Benchmarks/Cell/Cell.fs:37
  at Cell.test (Boolean doAs, Int32 m, Int32 n, Int32 p) [0x00000] in /Users/h/dev/haf/Hopac/Benchmarks/Cell/Cell.fs:206
  at <StartupCode$Cell>.$Cell.main@ () [0x00007] in /Users/h/dev/haf/Hopac/Benchmarks/Cell/Cell.fs:212
```

#### Known workarounds

No known workarounds.

#### Related information 

Provide any related information 

* Operating system, **OS X 10.10.5**
* Branch, **master**
* .NET Runtime, CoreCLR or Mono Version:

```
✗ mono --version
Mono JIT compiler version 4.2.3 (Stable 4.2.3.4/832de4b Wed Mar 30 13:57:21 PDT 2016)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           normal
	SIGSEGV:       altstack
	Notification:  kqueue
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug
	LLVM:          supported, not enabled.
	GC:            sgen
```

* Editing Tools (e.g. Visual Studio Version)

FAKE, Paket

* Indications of severity

Major, stops signed packages from being created with the F# language.
Comment 1 henrik 2016-05-17 07:35:59 UTC
Any update on this?