Date: Wed, 04 May 2011 10:52:03 +0100 From: David Woodhouse <dwmw2@infradead.org> To: Matthias Apitz <guru@unixarea.de> Cc: gnome@freebsd.org, evolution-list@gnome.org Subject: Re: [Evolution] evolution-2.32.1 (FreeBSD HEAD) && calendar not working Message-ID: <1304502723.6400.114.camel@macbook.infradead.org> In-Reply-To: <20110504094447.GA30294@sh4-5.1blu.de> References: <20110426213920.GA15678@sh4-5.1blu.de> <20110427062214.GA1159@sh4-5.1blu.de> <20110428073857.GB4359@sh4-5.1blu.de> <20110428131312.GA17412@sh4-5.1blu.de> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2011-05-04 at 11:44 +0200, Matthias Apitz wrote: > I have inserted some fprintf's in read_conf() to print in hex the memory > of the hash_table (see below); it matches what gdb reads about the > hash_table (values marked with ^^^); Was that *right* after the g_hash_table_new() call? 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*. -- dwmw2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1304502723.6400.114.camel>