GNOME Bugzilla – Bug 668872
valgrind invalid read errors
Last modified: 2018-08-17 13:59:11 UTC
Using gconf-editor and gconf 3.2.3 on Ubuntu: "==26565== Invalid read of size 4 ==26565== at 0x40681C7: gconf_entry_get_key (gconf-value.c:1610) ==26565== by 0x805A0CF: gconf_list_model_get_value (gconf-list-model.c:276) ==26565== by 0x432440F: gtk_tree_model_get_value (gtktreemodel.c:1394) ==26565== by 0x432E7E2: gtk_tree_model_sort_get_value (gtktreemodelsort.c:1368) ==26565== by 0x432440F: gtk_tree_model_get_value (gtktreemodel.c:1394) ==26565== by 0x4325443: gtk_tree_model_get_valist (gtktreemodel.c:1766) ==26565== Address 0x7ea3038 is 0 bytes inside a block of size 20 free'd ==26565== at 0x402906C: free (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==26565== by 0x482C81A: standard_free (gmem.c:98) ==26565== by 0x482C98F: g_free (gmem.c:252) ==26565== by 0x4840DBA: g_slice_free1 (gslice.c:1111) ==26565== by 0x4065993: gconf_entry_unref (gconf-value.c:1532) ==26565== by 0x805A290: gconf_list_model_set_root_path (gconf-list-model.c:142) ==26565== by 0x805421E: gconf_editor_window_selection_changed (gconf-editor-window.c:906) ==26565== by 0x47A053B: g_cclosure_marshal_VOID__VOID (gmarshal.c:85) ==26565== by 0x479EF8B: g_closure_invoke (gclosure.c:774) ==26565== by 0x47B0844: signal_emit_unlocked_R (gsignal.c:3302) ==26565== by 0x47B80C1: g_signal_emit_valist (gsignal.c:3033) ==26565== by 0x77F4217: ??? ==26565== ==26565== Invalid read of size 1 ==26565== at 0x481673A: g_str_hash (ghash.c:1709) ==26565== by 0x4815CA7: g_hash_table_lookup (ghash.c:388) ==26565== by 0x406A282: gconf_client_lookup (gconf-client.c:2359) ==26565== by 0x406B5EF: get (gconf-client.c:1474) ==26565== by 0x406D079: gconf_client_get_entry (gconf-client.c:1577) ==26565== by 0x805BB2C: gconf_client_get_schema_for_key (gconf-util.c:87) ==26565== by 0x80538CC: gconf_editor_window_update_list_selection (gconf-editor-window.c:1136) ==26565== by 0x47A053B: g_cclosure_marshal_VOID__VOID (gmarshal.c:85) ==26565== by 0x479EF8B: g_closure_invoke (gclosure.c:774) ==26565== by 0x47B0844: signal_emit_unlocked_R (gsignal.c:3302) ==26565== by 0x47B80C1: g_signal_emit_valist (gsignal.c:3033) ==26565== by 0x5A5942F: ??? ==26565== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==26565== Access not within mapped region at address 0x0 ==26565== at 0x481673A: g_str_hash (ghash.c:1709) ==26565== by 0x4815CA7: g_hash_table_lookup (ghash.c:388) ==26565== by 0x406A282: gconf_client_lookup (gconf-client.c:2359) ==26565== by 0x406B5EF: get (gconf-client.c:1474) ==26565== by 0x406D079: gconf_client_get_entry (gconf-client.c:1577) ==26565== by 0x805BB2C: gconf_client_get_schema_for_key (gconf-util.c:87) ==26565== by 0x80538CC: gconf_editor_window_update_list_selection (gconf-editor-window.c:1136) ==26565== by 0x47A053B: g_cclosure_marshal_VOID__VOID (gmarshal.c:85) ==26565== by 0x479EF8B: g_closure_invoke (gclosure.c:774) ==26565== by 0x47B0844: signal_emit_unlocked_R (gsignal.c:3302) ==26565== by 0x47B80C1: g_signal_emit_valist (gsignal.c:3033) ==26565== by 0x5A5942F: ???" gconf-editor seems to segfault quite easily on the current GNOME version...
the issue could be a gconf-editor or gtk one rather, with the current gtk the "changed" signal callback is called for several listview rows from the right side when the path is changed on the left
GConf has been deprecated since 2011. GConf is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/gconf/commits/master dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!