2.0.2 and GConf

[David Hampton]

On Wed, 2006-11-29 at 14:23 -0700, Mark Johnson wrote: 
> I ran gnucash --g-fatal-warnings, found the process, attached gdb.
> 
> Here is the backtrace, along with the value of the parameters from frame 6:
> (gdb) cont
> Continuing.
> 
> Program received signal SIGABRT, Aborted.
> [Switching to Thread -1229989664 (LWP 28567)]
> 0xb6b5a027 in raise () from /lib/tls/libc.so.6
> (gdb) bt
> #0  0xb6b5a027 in raise () from /lib/tls/libc.so.6
> #1  0xb6b5b747 in abort () from /lib/tls/libc.so.6
> #2  0xb6cc0b0d in g_logv () from /usr/lib/libglib-2.0.so.0
> #3  0xb6cc0b36 in g_log () from /usr/lib/libglib-2.0.so.0
> #4  0xb750368b in gconf_listeners_remove_if () from /usr/lib/libgconf-2.so.4
> #5  0xb751356f in gconf_client_notify_remove () from 
> /usr/lib/libgconf-2.so.4
> #6  0xb7529807 in gnc_gconf_remove_notification (object=0x814d940, 
> section=0x0, whoami=0x809aeb0 "\030Ý\t\b\017")
>     at gnc-gconf-utils.c:867
> #7  0xb7e3410b in gnc_main_window_destroy (object=0x814d940) at 
> gnc-main-window.c:1817

The #6 call frame shouldn't be possible.  The calling function passes a
constant string to gnc_gconf_remove_notification as the section name,
and has done so since that argument was added to the function.  You're
also showing garbage for the whoami argument, another a constant string.
Any chance you have another copy of gnucash on your system, or didn't
get a complete compile of the tree?

David