Hi, On Mo, 2015-08-31 at 16:41 +0100, jnqnfe wrote: > On Mon, 2015-08-31 at 17:36 +0300, Sebastian Dröge wrote: > > On Mo, 2015-08-31 at 15:29 +0100, jnqnfe wrote: > > > > > > > Can someone who is still able to reproduce this with 1.5.90 > > > > from > > > > experimental also install debug symbols for libc6, libglib2.0 > > > > -0, > > > > all the GStreamer packages and then > > > > a) run with valgrind --track-origins=yes > > > > b) get a new backtrace with gdb? > > > > > > > > Thanks! > > > > > > I do not believe anyone has reported being able to reproduce the > > > issue with 1.5.90 packages. > > > > > > Do you want me to revert to the troublesome packages and get a > > > more > > > complete bt for you? > > > > That would be great, yes. Thanks :) > > Ok, pasted below! (full bt further down) > > #0 0x00007fff97f50ff0 in gst_memory_unmap (mem=0x7fff00000000, > info=info@entry=0x7fff87867980) at gstmemory.c:339 > #1 0x00007fff97f26f76 in gst_buffer_unmap (buffer=<optimized out>, > info=0x7fff87867980) at gstbuffer.c:1622 > #2 0x00007fff85442294 in gst_faad_set_format (dec=0x7fffc3399aa0 > [GstFaad], caps=<optimized out>) at gstfaad.c:326 > [...]
Interesting... that doesn't make any sense unless something corrupted the stack :) Can you also run in valgrind with --track-origins=yes and provide the log?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ pkg-gstreamer-maintainers mailing list pkg-gstreamer-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gstreamer-maintainers
