After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 72818 - Crash on notifications
Crash on notifications
Status: RESOLVED FIXED
Product: GConf
Classification: Deprecated
Component: gconf
CVS HEAD
Other other
: Normal normal
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-02-27 12:34 UTC by Rodrigo Moya
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rodrigo Moya 2002-02-27 12:34:05 UTC 
I set up a listener on a GConf directory. Then, in other part of the code,
I call gconf_client_set_string for several entries in that directory. And,
when the notification is supposed to be fired up (the entry is actually
stored), I get a crash, with the following backtrace:

+ Trace 18380

  • #0 ??
  • #1 notify_listeners_callback
    at gconf-client.c line 2351
  • #2 notify_listener_list
    at gconf-listeners.c line 588
  • #3 ltable_notify
    at gconf-listeners.c line 654
  • #4 gconf_listeners_notify
    at gconf-listeners.c line 184
  • #5 notify_one_entry
    at gconf-client.c line 2376
  • #6 gconf_client_flush_notifies
    at gconf-client.c line 2416
  • #7 notify_idle_callback
    at gconf-client.c line 2310
  • #8 g_idle_dispatch
    at gmain.c line 3128
  • #9 g_main_dispatch
    at gmain.c line 1616
  • #10 g_main_context_dispatch
    at gmain.c line 2160
  • #11 g_main_context_iterate
    at gmain.c line 2241
  • #12 g_main_loop_run
    at gmain.c line 2461
  • #13 gtk_main
    at gtkmain.c line 882
  • #14 bonobo_ui_main
    at bonobo-ui-main.c line 135
  • #15 gnome_db_main_run
    at gnome-db-init.c line 165
  • #16 main
    at main.c line 49
  • #17 __libc_start_main
    from /lib/libc.so.6 

The notification callback in my code calls gconf_client_get_*, and nothing
else. I'm not sure though it is being even called, since the crash seems to
happen before it gets called.
Comment 1 Havoc Pennington 2002-02-27 13:09:58 UTC 
"#0  0x00000003 in ?? ()" looks like it's calling "3" as a function
pointer; can you go to frame #1 and do a "list" and print the 
relevant-looking variables, and try to confirm exactly what is broken 
that causes the segv?
Comment 2 Rodrigo Moya 2002-03-03 15:58:04 UTC 
Sorry, was my fault :-) I was using, in the call to
gconf_client_notify_add 'listener_data->user_data', where it should
have been 'listener_data'