[Bug 782812] gst_element_factory_make: Program received signal SIGSEGV, Segmentation fault. g_slice_alloc (mem_size=mem_size at entry=368)

[GStreamer (GNOME Bugzilla)]

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

--- Comment #2 from minfrin at sharp.fm ---
Alas, no luck with valgrind:

==22184== Memcheck, a memory error detector
==22184== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==22184== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==22184== Command: gst-launch-1.0 --gst-debug-no-color
--gst-debug=1,GST_TRACER:7,GST_REFCOUNTING:0,GST_PADS:1,GST_STATES:5,tdttsparse:5,tsdemux:1,omx:1,omxvideo:1,omxvideodec:1,omxh264dec:1,omxvideoenc:1,omxh264enc:1,videoencoder:1,videorate:1,videoscale:1,mpegtsmux:4,decodebin:1,encodebin:1,h264parse:1,transcoder:5,hlssink:5
udpsrc multicast-iface=eth0 uri=udp://239.106.0.6:1234
caps=application/x-rtp,media=(string)video,clock-rate=(int)90000 ! rtpbin !
rtpmp2tdepay ! progressreport update-freq=5 ! transcoder name=transcoder !
capsfilter caps=video/x-raw ! transcoder. transcoder. ! capsfilter
caps=video/mpegts ! hlssink target-duration=0
==22184== 
disInstr(arm): unhandled instruction: 0xE734F817
                 cond=14(0xE) 27:20=115(0x73) 4:4=1 3:0=7(0x7)
==22184== valgrind: Unrecognised instruction at address 0x535bbc0.
==22184==    at 0x535BBC0: __udivmoddi4 (libgcc2.c:1078)
==22184==    by 0x5359777: ??? (bpabi.S:258)
==22184==    by 0x491D857: __sanitizer::AppendNumber(char**, char const*,
unsigned long long, unsigned char, unsigned char, bool, bool)
(sanitizer_printf.cc:59)
==22184== Your program just tried to execute an instruction that Valgrind
==22184== did not recognise.  There are two possible reasons for this.
==22184== 1. Your program has a bug and erroneously jumped to a non-code
==22184==    location.  If you are running Memcheck and you just saw a
==22184==    warning about a bad jump, it's probably your program's fault.
==22184== 2. The instruction is legitimate but Valgrind doesn't handle it,
==22184==    i.e. it's Valgrind's fault.  If you think this is the case or
==22184==    you are not sure, please let us know and we'll try to fix it.
==22184== Either way, Valgrind will now raise a SIGILL signal which will
==22184== probably kill your program.
==22184== 
==22184== Process terminating with default action of signal 4 (SIGILL)
==22184==  Illegal opcode at address 0x535BBC0
==22184==    at 0x535BBC0: __udivmoddi4 (libgcc2.c:1078)
==22184==    by 0x5359777: ??? (bpabi.S:258)
==22184==    by 0x491D857: __sanitizer::AppendNumber(char**, char const*,
unsigned long long, unsigned char, unsigned char, bool, bool)
(sanitizer_printf.cc:59)
==22184== Jump to the invalid address stated on the next line
==22184==    at 0x0: ???
==22184==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==22184== 
==22184== 
==22184== Process terminating with default action of signal 11 (SIGSEGV)
==22184==  Bad permissions for mapped region at address 0x0
==22184==    at 0x0: ???
==22184== 
==22184== HEAP SUMMARY:
==22184==     in use at exit: 0 bytes in 0 blocks
==22184==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==22184== 
==22184== All heap blocks were freed -- no leaks are possible
==22184== 
==22184== For counts of detected and suppressed errors, rerun with: -v
==22184== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault

The crash reported inside valgrind appears to be a crash inside
AddressSanitizer, it is not clear whether AddressSanitizer has crashed or
whether valgrind genuinely doesn't understand the instructions.

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