From owner-freebsd-gnome@FreeBSD.ORG Wed May 4 11:59:15 2011 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97E411065670 for ; Wed, 4 May 2011 11:59:15 +0000 (UTC) (envelope-from ftp51246-2575596@sh4-5.1blu.de) Received: from sh4-5.1blu.de (sh4-5.1blu.de [213.83.63.54]) by mx1.freebsd.org (Postfix) with ESMTP id 211E48FC1B for ; Wed, 4 May 2011 11:59:14 +0000 (UTC) Received: from ftp51246-2575596 by sh4-5.1blu.de with local (Exim 4.50) id 1QHajO-0005cL-Hy; Wed, 04 May 2011 13:59:02 +0200 Date: Wed, 4 May 2011 13:59:02 +0200 From: Matthias Apitz To: David Woodhouse Message-ID: <20110504115901.GA9185@sh4-5.1blu.de> References: <1303998164.2912.123.camel@macbook.infradead.org> <20110428140106.GA5664@sh4-5.1blu.de> <1303999409.2912.129.camel@macbook.infradead.org> <20110428145451.GA25158@sh4-5.1blu.de> <1304003620.4772.16.camel@macbook.infradead.org> <20110429084846.GA2763@sh4-5.1blu.de> <20110504094447.GA30294@sh4-5.1blu.de> <1304502723.6400.114.camel@macbook.infradead.org> <20110504104528.GA24928@sh4-5.1blu.de> <1304506085.6400.128.camel@macbook.infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1304506085.6400.128.camel@macbook.infradead.org> X-Operating-System: FreeBSD 7.0-RELEASE (i386) User-Agent: Mutt/1.5.9i Cc: gnome@freebsd.org, evolution-list@gnome.org Subject: Re: [Evolution] evolution-2.32.1 (FreeBSD HEAD) && calendar not working X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2011 11:59:15 -0000 El día Wednesday, May 04, 2011 a las 11:48:05AM +0100, David Woodhouse escribió: > On Wed, 2011-05-04 at 12:45 +0200, Matthias Apitz wrote: > > > That would seem to imply that your hash table was buggered from the very > > > beginning. If you really can't get gdb to work properly and use a > > > hardware watchpoint, try littering similar printfs all the way through > > > g_hash_table_new() so you can find out why it isn't being set to the > > > function you *provided*. > > > > will do ... > > The other thing to try is valgrind. > > Run in valgrind with GSLICE=always-malloc and that may catch some > use-after-free and other memory corruptions which could be causing this. valgrind itself crashes with sig11; I think g_hash_table_new() is not causing this problem; see the addr of e2k_ascii_strcase_hash() which read_config() hands over to it; it's exactly the broken one 0x29ed1f6b and set into the hash_table: Server is up and running... DEBUG e2k-autoconfig: entered read_config() DEBUG e2k-autoconfig: entering now g_hash_table_new(e2k_ascii_strcase_hash, e2k_ascii_strcase_equal): 29ed1f6b, 29ed1f39 DEBUG e2k-autoconfig: right after g_hash_table_new() DEBUG e2k-autoconfig: read_config() config_options=2995efb0: 00000008 00000007 00000007 00000000 00000000 2a57f280 29ed1f6b 29ed1f39 DEBUG e2k-autoconfig: read_config() return, fd=-1 DEBUG e2k-autoconfig: read_config() config_options=2995efb0: 00000008 00000007 00000007 00000000 00000000 2a57f280 29ed1f6b 29ed1f39 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 29804300 (LWP 100272/initial thread)] 0x29ed1f6b in ?? () (gdb) p *0x29ed1f6b Error accessing memory address 0x29ed1f6b: Dirección incorrecta. (gdb) -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/