From owner-freebsd-gnome@FreeBSD.ORG Mon Oct 6 16:57:49 2003 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 858E416A4B3 for ; Mon, 6 Oct 2003 16:57:49 -0700 (PDT) Received: from python.evilrealms.net (evilrealms.demon.co.uk [62.49.12.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 954C043F75 for ; Mon, 6 Oct 2003 16:57:48 -0700 (PDT) (envelope-from jay@evilrealms.net) Received: from evilrealms.net (viper [192.168.1.2]) by python.evilrealms.net (Postfix) with ESMTP id 9351351; Tue, 7 Oct 2003 00:57:47 +0100 (BST) Message-ID: <3F820179.80100@evilrealms.net> Date: Tue, 07 Oct 2003 00:57:45 +0100 From: Jay Cornwall User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joe Marcus Clarke References: <3F81E292.8070308@evilrealms.net> <1065477237.748.95.camel@gyros> In-Reply-To: <1065477237.748.95.camel@gyros> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD GNOME Users Subject: Re: FreeBSD Current lang/mono runtime problems X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2003 23:57:49 -0000 Joe Marcus Clarke wrote: >>[jay@python mono]$ mcs --version >>Mono C# compiler version 0.27.0.0 >> >>And never finishes. I tried to get an strace, but that seems to have >>issues with a missing /proc filesystem. Is there any more useful >>information I can obtain under FreeBSD to help debug this? > Mono doesn't work on FreeBSD. The problem seems to be in the garbage > collector. If you build mono without GC, it should work okay (but never > release memory). Ah, hmm. > Honestly, gnome@ doesn't really want mono since no one here is really a > C# user. We are keeping it since one of our developers, Juli Mallett, > has been busy, but wants to get back into Mono. In the meantime, if you > want to look at improving boehm-gc on FreeBSD, I'm sure your > contributions will not be turned down. Well I've had a brief look tonight, but free time is a little on the short side at the moment. It seems a segfault occurs inside mono-0.28/mono/mini.c:7291, sigusr1_signal_handler(). In order to identify the thread (through mono_current_thread()), mono/metadata/threads.c stores the MonoThread * in a thread-local structure using pthread_setspecific in previously called methods of mono/metadata/threads.c. Dropping in a few debug statements shows that a thread is entering sigusr1_signal_handler() that hasn't previously had its MonoThread * set (it may not even be a MonoThread, for all I know). That's the direct reason for the crash - to find the indirect reason, i.e. why this thread is entering without its MonoThread * set, will take me a bit longer. Enough technobabble, I'll try and find the bug and fix it! -- Cheers, Jay http://www.evilrealms.net/ - Systems Administrator & Developer http://www.ic.ac.uk/ - Imperial College, 2nd year CS student