[Mono-dev] Multiple Segfaults on mono 1.1.13.6
Hi all, I am getting a segfault with the mono runtime, and since I couldn't find it in bugzilla, thought I would check with the list if it has been fixed. Unfortunately, the program is proprietary, so I cannot hand out the source. If more details are required however, I can try and isolate it more ... Other important details are that I compile the program using the Microsoft compiler ... I have not tested it with the mono compiler. The program loads some config, connects to a network socket via an asynchronous tcp connection, does a bunch of things, and then exits. It segfaults if I call Environment.Exit(1), rather than exiting cleanly. I think it does not segfault when I explicitly Disconnect the socket before exiting. Yeah, ugly code not to disconnect, but it shouldn't crash the runtime ... This is what the backtrace looks like: #0 0x006becae in __pthread_mutex_lock (mutex=0x74c008) at pthread_mutex_lock.c:76 #1 0x08108242 in mono_once () #2 0x080da7bf in mono_jit_info_table_find () #3 0x0813ba64 in mono_codegen () #4 signal handler called #5 0x080a5222 in mono_thread_pool_remove_socket () #6 0x080a42e3 in mono_debug_address_from_il_offset () #7 0x08099ff2 in mono_thread_get_tls_offset () #8 0x080f5227 in mono_environment_exitcode_set () #9 0x08113945 in GC_end_blocking () #10 0x006bd341 in start_thread (arg=0x1963bb0) at pthread_create.c:261 #11 0x004176fe in ?? () from /lib/tls/libc.so.6 Ah, actually, after I change the code to explicitly call Disconnect on the sockets before calling Environment.Exit(1), I am now getting a different segfault ... #0 0x003367a2 in ?? () at rtld.c:576 from /lib/ld-linux.so.2 576 relocate_doit (void *a) (gdb) where #0 0x003367a2 in ?? () at rtld.c:576 from /lib/ld-linux.so.2 #1 0x003777d5 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:67 #2 0x00379149 in *__GI_abort () at ../sysdeps/generic/abort.c:88 #3 0x0814f73b in mono_handle_native_sigsegv () #4 0x0813ba8f in mono_codegen () #5 signal handler called #6 0x0813bad4 in mono_codegen () #7 signal handler called #8 0x003367a2 in ?? () at rtld.c:576 from /lib/ld-linux.so.2 #9 0x006c213e in ?? () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:57 from /lib/tls/libpthread.so.0 #10 0x081bf1c8 in stderr () #11 0x006c6ff4 in ?? () from /lib/tls/libpthread.so.0 #12 0x01275bb0 in ?? () #13 0x006beda7 in ?? () from /lib/tls/libpthread.so.0 #14 0x01275318 in ?? () #15 0x081beb10 in ?? () #16 0x08216300 in ?? () #17 0xb7e01b90 in ?? () #18 0x01275328 in ?? () #19 0x08108242 in mono_once () #20 0x08108242 in mono_once () #21 0x08099e18 in mono_thread_get_tls_offset () #22 0x08099ea7 in mono_thread_get_tls_offset () #23 0x0809a00f in mono_thread_get_tls_offset () #24 0x080f5227 in mono_environment_exitcode_set () #25 0x08113945 in GC_end_blocking () #26 0x006bd341 in start_thread (arg=0x1275bb0) at pthread_create.c:261 #27 0x004176fe in ?? () from /lib/tls/libc.so.6 mono --version Mono JIT compiler version 1.1.13.6, (C) 2002-2005 Novell, Inc and Contributors. www.mono-project.com TLS: normal GC:Included Boehm (with typed GC) SIGSEGV : normal uname -a: Linux 2.6.10-1.741_FC3smp #1 SMP Thu Jan 13 16:53:16 EST 2005 i686 i686 i386 GNU/Linux The machine has 4 intel xeon cpus. Cheers, Andrew ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Multiple Segfaults on mono 1.1.13.6
On Tue, 2006-05-16 at 16:08 +1000, [EMAIL PROTECTED] wrote: Hi all, I am getting a segfault with the mono runtime, and since I couldn't find it in bugzilla, thought I would check with the list if it has been fixed. Unfortunately, the program is proprietary, so I cannot hand out the source. If more details are required however, I can try and isolate it more ... Other important details are that I compile the program using the Microsoft compiler ... I have not tested it with the mono compiler. The program loads some config, connects to a network socket via an asynchronous tcp connection, does a bunch of things, and then exits. It segfaults if I call Environment.Exit(1), rather than exiting cleanly. I think it does not segfault when I explicitly Disconnect the socket before exiting. Yeah, ugly code not to disconnect, but it shouldn't crash the runtime ... Environment.Exit() causing a crash rings a bell, but I can't think of the specifics right now. This is what the backtrace looks like: #0 0x006becae in __pthread_mutex_lock (mutex=0x74c008) at pthread_mutex_lock.c:76 #1 0x08108242 in mono_once () #2 0x080da7bf in mono_jit_info_table_find () #3 0x0813ba64 in mono_codegen () #4 signal handler called #5 0x080a5222 in mono_thread_pool_remove_socket () #6 0x080a42e3 in mono_debug_address_from_il_offset () #7 0x08099ff2 in mono_thread_get_tls_offset () #8 0x080f5227 in mono_environment_exitcode_set () #9 0x08113945 in GC_end_blocking () #10 0x006bd341 in start_thread (arg=0x1963bb0) at pthread_create.c:261 #11 0x004176fe in ?? () from /lib/tls/libc.so.6 That backtrace looks fairly garbled to me. Is this extracted from a core dump or did you run your app through gdb? Ah, actually, after I change the code to explicitly call Disconnect on the sockets before calling Environment.Exit(1), I am now getting a different segfault ... That trace doesn't help much either. mono --version Mono JIT compiler version 1.1.13.6, (C) 2002-2005 Novell, Inc and Contributors. Could you try a newer version (either later 1.1.13 or head), compiled with debugging symbols? And if you extracted the backtrace from a core dump, running it in gdb might generate better information. You need to tell gdb: handle SIGPWR SIGXCPU nostop noprint pass before you start executing. The machine has 4 intel xeon cpus. Does anything change if you run on a single processor machine? - Dick signature.asc Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono remoting error on an embedded arm system
An: mono-devel-list@lists.ximian.com Betreff: [Mono-dev] Mono remoting on an embedded arm system Hello All, we are running mono 1.1.14 on an embedded arm system with remoting services to communicate with a host system. The client on the hostmachine or localy started has no problem to communicate with the embedded server. But if a remote-called method throws an exception, this exception will be catched/shown on the server and not on the remote client. If we run the same code with mono on linux or win32 the exception is thrown on the client (as it should). So I think there is some missing configuration file or something else. Hi, I compared the function call traces (mono -v) of the arm and x86 version and they differ after throwing the exception, it looks like the code resumes in different catch() clauses. On the x86 systems it's the catch() clause of the RemotingServices:InternalExecute Function and on the arm system it seems to be the catch all clause of the RemotingServices thread. So is this possibly an exception handling error specific to the Arm version ? Thanxs for every information on this issue. Greetings Leopold Faschalek - Research Development / Senior Software Developer SKIDATA AG Untersbergstraße 40 A-5083 Gartenau [P] +43(0)6246/888-0 [F] +43(0)6246/888-7 [e] [EMAIL PROTECTED] [w] www.skidata.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
AW: [Mono-dev] Mono remoting error on an embedded arm system
Von: Dave Cramer [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 17. Mai 2006 16:58 An: FALE(Leopold Faschalek) Betreff: Re: [Mono-dev] Mono remoting error on an embedded arm system can I ask you how you got mono built for the embedded arm? And which embedded arm device you are using ? Dave Hi Dave, I compile mono under the 'scratchbox' environment, this simulates an arm host on a x86 linux machine. It uses qemu to execute the arm code but this failes for running 'mono *.exe' files (eg the 'mono mcs.exe'). I think the jit'ed code is the problem. But the compiled mono seems to be ok (except this remoting exception error). The mscorlib.dll is under ./mcs/class/lib/monolite/mscorlib.dll and Other .exe and .dll files may be copied from a linux or windows mono installation. The arm cpu is an Atmel AT91RM9200 arm920T (v4t), the board is based on the AT91RM9200DK design. Greetings Leopold ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] new test framework works on dotnet
Hello, The attached patch adds new tests to the system.web testsuite, using the new test framework. The tests can be built on mono and run on mono or on dotnet by using the standard target make run-test-ondotnet. Some tests pass on Mono, but some of them need more effort. Sometimes mono vm stucks, I worked around that by adding Sleep at the beginning of each test. Some tests still fail. I added a custom target run-nunitweb-ondotnet and run-nunitweb-onmono to the makefile to run only the tests which use the new framework. So I'm looking for the help to make them all pass on mono, so we can run them as a part of a build. Andrew. NunitWeb.patch Description: NunitWeb.patch ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] new test framework works on dotnet
Hello, Some tests pass on Mono, but some of them need more effort. Sometimes mono vm stucks, I worked around that by adding Sleep at the beginning of each test. Some tests still fail. Mhm, very strange. Could you send a QUIT signal to the Mono process when it hangs? This will help pinpoint. I added a custom target run-nunitweb-ondotnet and run-nunitweb-onmono to the makefile to run only the tests which use the new framework. So I'm looking for the help to make them all pass on mono, so we can run them as a part of a build. Andrew. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Miguel de Icaza [EMAIL PROTECTED] ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Mono remoting on an embedded arm system
hello, we are running mono 1.1.14 on an embedded arm system with remoting services to communicate with a host system. This does not ring any bells; Could you cook a small test case, maybe include the exception, stack traces produced? ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
