[Bug 43425] New: 64-bit .NET application crashes with NullReferenceException

https://bugs.winehq.org/show_bug.cgi?id=43425

Bug ID: 43425
           Summary: 64-bit .NET application crashes with
                    NullReferenceException
           Product: Wine
           Version: 2.12
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P2
         Component: mscoree
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 58791
  --> https://bugs.winehq.org/attachment.cgi?id=58791
back trace of the bug

I encountered a problem with the 64-bit .NET Framework:

My C# program is very simple:

Code:
static void Main(string[] args)
{
    System.Console.WriteLine("Hello world!");
    Debug.WriteLine("Debug Hello world!");
}

I installed the WINE-2.12 64-bit on CentOS 7 (3.10.0-514.21.1.el7.x86_64) and
installed the .NET Framework 4.6.1 onto it. Before installing the .NET
Framework, I removed wine-mono. I got the following error message when I tried
to run the above program:

Hello world!

Unhandled Exception: System.NullReferenceException: Object reference not set to
an instance of an object.
at System.Diagnostics.DiagnosticsConfiguration.Initialize()
at System.Diagnostics.DiagnosticsConfiguration.get_IndentSize()
at System.Diagnostics.TraceInternal.InitializeSettings()
at System.Diagnostics.TraceInternal.WriteLine(String message)
at ConsoleApplication3.Program.Main(String[] args)
wine: Unhandled page fault on read access to 0x00000000 at address 0x1aa460fd
(thread 0009), starting debugger...

The problem is with the line "Debug.WriteLine(...)". However, the same
application compiled with 32-bit works well.

I found out that I got the similar error at other positions when I ran our
in-house 64-bit .NET program, even if I don't use Debug.WriteLine(...), so I
created the hello-world program to reproduce it.

My final goal is: run our 64-bit .NET application on a 64-bit WINE with .NET
Framework 4.6.1.

[Bug 43425] 64-bit .NET application crashes with NullReferenceException

https://bugs.winehq.org/show_bug.cgi?id=43425

Nikolay Sivov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|blocker                     |normal

[Bug 43425] 64-bit .NET application crashes with NullReferenceException

https://bugs.winehq.org/show_bug.cgi?id=43425

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
       Distribution|---                         |Red Hat
           Keywords|                            |dotnet, download, source,
                   |                            |testcase
          Component|mscoree                     |-unknown

--- Comment #1 from Austin English  ---
mscoree component is for wine's mscoree, i.e., wine-mono, not native .Net.

[Bug 43425] 64-bit .NET application crashes with NullReferenceException

https://bugs.winehq.org/show_bug.cgi?id=43425

--- Comment #2 from [e-mail] ---
Hi Austin,

thanks for the reply.

Yes, you're right. It is not really realted mscoree of wine. I just did not
know how to get an expert hooked to have a look at this problem. It is
definitely related to wine, since this 64-bit program just worked fine on
Windows and also fine with wine 32-bit.

Unfortunately your excellent winetricks cannot support 64-bit well. Perhaps you
have some insight into this kind of problems and could help me with that.

Sorry for having posted in this category.

/Kenny

[Bug 43425] 64-bit .NET application crashes with NullReferenceException

https://bugs.winehq.org/show_bug.cgi?id=43425

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Fabian Maurer  ---
Is this still a problem as of wine-2.22? Because I can't reproduce it.
If it's still existent, mind providing instructions as how to reproduce?
Especially how you installed dotnet.