[Mono-bugs] [Bug 460236] New: mono <dir> crashes

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Dec 18 10:29:13 EST 2008


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


           Summary: mono <dir> crashes
           Product: Mono: Runtime
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: rkvinge at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


It makes no sense to do so, but executing 'mono ~' (or mono <any directory>)
crashes:

rolf at linux:>mono ~

** (/home/rolf:20562): WARNING **: Thread (nil) may have been prematurely
finalized

** (/home/rolf:20562): WARNING **: Thread (nil) may have been prematurely
finalized
Stacktrace:


** (/home/rolf:20562): WARNING **: Thread (nil) may have been prematurely
finalized

** (/home/rolf:20562): WARNING **: Thread (nil) may have been prematurely
finalized

Native stacktrace:

        mono [0x80c81b9]
        mono [0x80f1b2b]
        [0xffffe410]
        mono [0x818ddf5]
        mono(mono_image_open_full+0xd1) [0x818df91]
        mono(mono_image_open+0x20) [0x818e070]
        mono [0x80fd4e4]
        mono [0x80fece5]
        mono [0x805d34f]
        mono(mono_main+0x399) [0x80afb29]
        mono [0x805acf1]
        /lib/libc.so.6(__libc_start_main+0xe5) [0xb7e3f5f5]
        mono [0x805ac21]

Debug info from gdb:

Cannot access memory at address 0x20
[Thread debugging using libthread_db enabled]
[New Thread 0xb7e276f0 (LWP 20562)]
0xffffe430 in __kernel_vsyscall ()
  1 Thread 0xb7e276f0 (LWP 20562)  0xffffe430 in __kernel_vsyscall ()

Thread 1 (Thread 0xb7e276f0 (LWP 20562)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb7f9eb83 in __read_nocancel () from /lib/libpthread.so.0
#2  0x080c8333 in mono_handle_native_sigsegv (signal=11, ctx=0xb7cf3d0c) at
mini-exceptions.c:1439
#3  0x080f1b2b in mono_arch_handle_altstack_exception (sigctx=0xb7cf3d0c,
fault_addr=0x0, stack_ovf=0) at exceptions-x86.c:864
#4  <signal handler called>
#5  0x0818d38b in do_mono_image_load (image=0x82b2a60, status=0x0,
care_about_cli=1) at image.c:793
#6  0x0818ddf5 in do_mono_image_open (fname=0xbfecf0cd "/home/rolf",
status=0x0, care_about_cli=1, refonly=0) at image.c:916
#7  0x0818df91 in mono_image_open_full (fname=0xbfecf0cd "/home/rolf",
status=0x0, refonly=0) at image.c:1172
#8  0x0818e070 in mono_image_open (fname=0xbfecf0cd "/home/rolf", status=0x0)
at image.c:1192
#9  0x080fd4e4 in get_runtimes_from_exe (exe_file=0xbfecf0cd "/home/rolf",
exe_image=0x828b4a4, runtimes=0xbfecdb00) at domain.c:2347
#10 0x080fece5 in mono_init_internal (filename=0xbfecf0cd "/home/rolf",
exe_filename=0xbfecf0cd "/home/rolf", runtime_version=0x0) at domain.c:1268
#11 0x0805d34f in mini_init (filename=0xbfecf0cd "/home/rolf",
runtime_version=0x0) at mini.c:5048
#12 0x080afb29 in mono_main (argc=2, argv=0xbfecdd54) at driver.c:1535
#13 0x0805acf1 in main (argc=) at main.c:34
#0  0xffffe430 in __kernel_vsyscall ()

=================================================================
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.
=================================================================

Aborted

rolf at linux:> mono --version
Mono JIT compiler version 2.3 (/trunk/mono r121766 Thu Dec 18 09:52:01 CET
2008)
Copyright (C) 2002-2008 Novell, Inc and Contributors. www.mono-project.com
        TLS:           __thread
        GC:            Included Boehm (with typed GC)
        SIGSEGV:       altstack
        Notifications: epoll
        Architecture:  x86
        Disabled:      none


-- 
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.


More information about the mono-bugs mailing list