[Mono-bugs] [Bug 419273] New: mini.c line 11697 (mini_select_instructions) should not be reached aborting...

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=419273


           Summary: mini.c line 11697 (mini_select_instructions) should not
                    be reached aborting...
           Product: Mono: Runtime
           Version: 2.0
          Platform: x86-64
        OS/Version: Windows Vista
            Status: NEW
          Severity: Blocker
          Priority: P5 - None
         Component: JIT
        AssignedTo: lupus at novell.com
        ReportedBy: ehj at briskwater.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Beta-Customer


First time using Mono.  Compiled our app which is stable in the Microsoft
environment using the cmd line below.

gmcs -out:App.exe -target:winexe -optimize -pkg:dotnet -r:"C:/program f
iles
(x86)/Mono-2.0/lib/mono/gac/System.Xml.Linq\3.5.0.0__b77a5c561934e089\System.Xml.Linq.dll"
*.cs @libs.rsp

(There is probably an easier way to get the xml linq library)

Executed the app with

mono App.exe

The application starts up, opens a number of normal windows.  The application
then spawns 8 computational threads. Within seconds 8 windows open up each with
multiple instances of:

** ERROR **: file mini.c line 11697 (mini_select_instructions) should not
be reached
aborting...

The application's window thread appears to still run but the computational
threads appear dead.

I don't know if this is related but the computational threads build and execute
dynamic methods.  It appears a handfull (30+) do execute to completion before
the errors show up.

Machine is 8 core Xeon, 16 GB, Vista Ultimate SP1


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.