Mark Johnson <[EMAIL PROTECTED]> writes:
> Mark Johnson wrote:
>
>> This does not look like the sort of thing that occurs when debugging
>> optimized code, but I am going to try a build without optimization
>> anyway.
>>
>>
>>
> Obviously, the optimization was interfering with debugging. Here is the
> gnucash terminal output:
> [EMAIL PROTECTED]:~$ gnucash --g-fatal-warnings
>
> GConf-CRITICAL **: file gconf-listeners.c: line 444 (ltable_remove):
> assertion `node != NULL' failed
> aborting...
This would seem to imply that we're trying to remove a listener
a second time, when the listener has already been removed. At
least that's my reading of the message.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
