GNOME Bugzilla – Bug 688533
symbol-db: g_value_copy() critical due to null values in database.
Last modified: 2013-02-27 22:21:23 UTC
The following assertion is due to src_value being GDA_TYPE_NULL but dest value being G_TYPE_INT. I've attached a patch that gets rid of this warning by fixing so that we never store any null values for scope_definition_id and scope_id. (anjuta:22387): GLib-GObject-CRITICAL **: g_value_copy: assertion `g_value_type_compatible (G_VALUE_TYPE (src_value), G_VALUE_TYPE (dest_value))' failed Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 0x2aaaae1e6940 (LWP 22387)] 0x00002aaaacfe7c30 in g_logv (log_domain=0x2aaaacd7eab0 "GLib-GObject", log_level=G_LOG_LEVEL_CRITICAL, format=0x2aaaad06cc4c "%s: assertion `%s' failed", args=0x7fffffffb678) at gmessages.c:967 967 G_BREAKPOINT (); (gdb) bt expression=0x2aaaacd7ec60 "g_value_type_compatible (G_VALUE_TYPE (src_value), G_VALUE_TYPE (dest_value))") at gmessages.c:1012
Created attachment 229237 [details] [review] symbol-db: don't allow or set null scope_definition_id and scope_id. Add not null constraints to the two fields and fixup PREP_QUERY_SYMBOL_NEW and PREP_QUERY_UPDATE_SYMBOL_SCOPE_ID so that they don't set the fields to null. The scope_id lookup in PREP_QUERY_SYMBOL_NEW can be removed since the call to sdb_engine_add_new_scope_definition() at symbol-db-engine-core.c:4830 already does the lookup.
Thanks, I'll have a look at the patch ASAP. The bug is really similar to #687054
Comment on attachment 229237 [details] [review] symbol-db: don't allow or set null scope_definition_id and scope_id. I've removed the version change "371.0" because we already are at 373.0
I've committed the patch, thanks.