GNOME Bugzilla – Bug 687099
GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed
Last modified: 2012-10-29 12:01:25 UTC
Running Debian Sid/unstable with self built Midori from Git (0.4.7+), starting Midori the following is printed to the command line. (midori4:7666): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed (midori4:7666): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (midori4:7666): libsoup-CRITICAL **: soup_header_free_param_list: assertion `param_list != NULL' failed Starting it with GDB and option `--g-fatal-warnings`, I was able to get the following backtrace and looking at it I think the problem lies within LibSoup and not Midori. But please correct me if I am wrong.
+ Trace 231099
Thread 1 (Thread 0xb38a2890 (LWP 18250))
Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=log_domain@entry=0xb7eec78e "GLib", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0xb7ef52a2 "%s: assertion `%s' failed", args1=args1@entry=0xbfffe94c "9\f\357\267@\n\357\267\070\303]\200h.[\200w\301^\267\330\340]\200f\211\356\267\364\257\365\267X\177鷎\307\356\267\071\f\357\267@\n\357\267<\003^\267\370j_\200") at /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gmessages.c:765 765 in /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gmessages.c Continuing. [Thread 0xb115cb70 (LWP 18274) exited] Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=log_domain@entry=0xb76105c7 "libsoup", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0xb7ef52a2 "%s: assertion `%s' failed", args1=args1@entry=0xbfffe97c "\002Oa\267\334Ma\267\300Y\377\267") at /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gmessages.c:765 765 in /build/buildd-glib2.0_2.33.12+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12+really2.32.4/./glib/gmessages.c Continuing.
*** This bug has been marked as a duplicate of bug 683433 ***