GNOME Bugzilla – Bug 745694
tests/custom-serialize,proxy-continuous segfault due to uninitialized GError pointers
Last modified: 2015-03-17 14:03:26 UTC
If you don't initialize GError pointers to NULL, a call fails for whatever reason, and the error gets set, the following happens: (process:1416): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Connection terminated unexpectedly Call failed: MANPATH=/etc/java-config-2/current-system-vm/man:/usr/local/share/man:/usr/share/man:/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.2/man:/usr/share/binutils-data/x86_64-pc-linux-gnu/2.25/man:/etc/java-config-2/current-system-vm/man/:/usr/lib64/php5.6/man/:/usr/share/postgresql/man/:/usr/share/postgresql-9.4/man/:/usr/share/postgresql-9.3/man/:/usr/share/rust-1.0.0_alpha2/man Program received signal SIGSEGV, Segmentation fault. 0xf785e3d0 in __GI___libc_free (mem=0xffffc894) at malloc.c:2944 2944 ar_ptr = arena_for_chunk (p); (gdb) bt
+ Trace 234789
Created attachment 298655 [details] [review] simple patch to fix this
Review of attachment 298655 [details] [review]: Good catch, thanks