[Mono-bugs] [Bug 332866] New: Runtime exits without error message on vbnc compiled program.

[bugzilla_noreply at novell.com]

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

           Summary: Runtime exits without error message on vbnc compiled
                    program.
           Product: Mono: Runtime
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at ximian.com
        ReportedBy: andyhume32 at yahoo.co.uk
         QAContact: mono-bugs at ximian.com
          Found By: ---


Created an attachment (id=177611)
 --> (https://bugzilla.novell.com/attachment.cgi?id=177611)
Repro assembly

Running the attached assembly results in mono.exe SVN head on Win32 exiting
with only: 
[[
Stacktrace:
]]

That's by default, and also with --debug.  

However if one adds --trace, it fails with MessageBox:
[[
---------------------------
Error
---------------------------

** ERROR **: file loader.c: line 1796 (mono_method_signature): assertion
failed: (mono_metadata_token_table (m->token) == MONO_TABLE_METHOD)
aborting...

---------------------------
OK   
---------------------------
]]
and on the console:
[[
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
]]

On 1.2.5 Win32 and Suse VM by default it hangs.  On Win32 with "--trace" one
sees the console message as above, and on Suse VM one sees:


AAATTAAACCCHHH
[[
Stacktrace:


Native stacktrace:

        mono [0x81681c0]
        mono [0x8134ca2]
        [0xb7f9c440]
        [0xb7469f26]
        [0xb7469ed2]
        [0xb7469e56]
        [0xb7466ff7]
        [0xb7463876]
        [0xb7463124]
        [0xb7462fdc]
        mono [0x8154f36]
        mono(mono_runtime_invoke+0x27) [0x80927b7]
        mono(mono_runtime_exec_main+0xb0) [0x80966e0]
        mono(mono_runtime_run_main+0x215) [0x8096dd5]
        mono(mono_main+0xa15) [0x8058e25]
        mono [0x8057f0e]
        /lib/libc.so.6(__libc_start_main+0xdc) [0xb7d8df9c]
        mono [0x8057e51]

Debug info from gdb:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1210652048 (LWP 20409)]
[New Thread -1220158576 (LWP 20411)]
[New Thread -1220072560 (LWP 20410)]
0xb7f9c410 in ?? ()
  3 Thread -1220072560 (LWP 20410)  0xb7f9c410 in ?? ()
  2 Thread -1220158576 (LWP 20411)  0xb7f9c410 in ?? ()
  1 Thread -1210652048 (LWP 20409)  0xb7f9c410 in ?? ()

Thread 3 (Thread -1220072560 (LWP 20410)):
#0  0xb7f9c410 in ?? ()
#1  0xb74723a8 in ?? ()
#2  0x08203584 in __JCR_LIST__ ()
#3  0x00000000 in ?? ()

Thread 2 (Thread -1220158576 (LWP 20411)):
#0  0xb7f9c410 in ?? ()
#1  0xb745d1a8 in ?? ()
#2  0x00000001 in ?? ()
#3  0x00000000 in ?? ()

Thread 1 (Thread -1210652048 (LWP 20409)):
#0  0xb7f9c410 in ?? ()
#1  0xbfb49cfc in ?? ()
#2  0x00000000 in ?? ()
#0  0xb7f9c410 in ?? ()


=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================
]]


Firstly can the fault with the assembly be diagnosed so the problem can be
reported to vbnc.  Secondly shouldn't the runtime report an error even without
the "--trace" option.  (Is even that message just an artifact from the
logging).

The assembly is a very simple WinForms app created in VS2005 and compiled with
vbnc SVN head.

BTW it fails on MSFT CLR with 
[[
Unhandled Exception: System.AccessViolationException: Attempted to read or
write protected memory. This is often an indication that other memory is
corrupt.
]]


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