[Bug 739312] gst_init segmentation fault

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=739312

GstBlub <gstblub at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gstblub at gmail.com

--- Comment #9 from GstBlub <gstblub at gmail.com> ---
I just ran into this bug with 1.6.3 on an x86 based box with glibc 2.19 and
glib2 2.40.0:

Program received signal SIGSEGV, Segmentation fault.
0xb7697cf0 in g_datalist_id_dup_data (datalist=datalist at entry=0x8295438,
key_id=key_id at entry=233, dup_func=dup_func at entry=0x0,
user_data=user_data at entry=0x0) at gdataset.c:864
864    gdataset.c: No such file or directory.
(gdb) bt
#0  0xb7697cf0 in g_datalist_id_dup_data (datalist=datalist at entry=0x8295438,
key_id=key_id at entry=233, dup_func=dup_func at entry=0x0,
user_data=user_data at entry=0x0) at gdataset.c:864
#1  0xb7697d84 in g_datalist_id_get_data (datalist=datalist at entry=0x8295438,
key_id=233) at gdataset.c:798
#2  0xb7793e41 in g_object_new_internal (class=class at entry=0x829533c,
params=params at entry=0x0, n_params=n_params at entry=0) at gobject.c:1731
#3  0xb7795bb1 in g_object_newv (object_type=object_type at entry=136912228,
n_parameters=n_parameters at entry=0, parameters=parameters at entry=0x0) at
gobject.c:1868
#4  0xb7796280 in g_object_new (object_type=136912228, first_property_name=0x0)
at gobject.c:1568
#5  0xb72db630 in _priv_gst_allocator_initialize () at gstallocator.c:587
#6  0xb72d5b51 in init_post (context=0x828ae7c, group=0x828b8dc, data=0x0,
error=0xbffff9ac) at gst.c:580
#7  0xb76bfed0 in g_option_context_parse (context=0x828ae7c, argc=0x0,
argv=0x0, error=0xbffff9ac) at goption.c:2085
#8  0xb72d5544 in gst_init_check (argc=0x0, argv=0x0, err=0xbffff9ac) at
gst.c:352
#9  0xb72d55a6 in gst_init (argc=0x0, argv=0x0) at gst.c:398
...

A breakpoint on g_mem_set_vtable() did not hit prior to this crash.  I run into
it 100% of the time when I use glibc's __malloc_hook/__free_hook/__realloc_hook
to track memory allocations.  Running it with valgrind (without using using
these hooks) has not yielded any complaints.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.