Segmentation fault with lib_mp4_parser_arm11_elinux_hfp.so.3.2

cancel
Showing results for 
Search instead for 
Did you mean: 

Segmentation fault with lib_mp4_parser_arm11_elinux_hfp.so.3.2

228 Views
aymensghaier
NXP Employee
NXP Employee

Dear all,

I am working with the Linux BSP Rev. L4.1.15_1.1.0-ga, on an iMX6 Quadplus based board, and with imx-parser package 4.1.4.

While playing the attached m4a file "B.m4a" with the following command :

gst-launch-1.0 -v  filesrc location=B.m4a   ! decodebin ! audioconvert ! volume ! fakesink

I got a segmentation fault error in "lib_mp4_parser_arm11_elinux_hfp.so.3.2":

(gdb) run
Starting program: /usr/bin/gst-launch-1.0 -v filesrc location=B.m4a \! decodebin \! audioconvert \! volume \! fakesink
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Setting pipeline to PAUSED ...
[New Thread 0x7675f470 (LWP 803)]
Pipeline is PREROLLING ...
[New Thread 0x75f5f470 (LWP 804)]
/GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstTypeFindElement:typefind.GstPad:src: caps = "video/quicktime\,\ variant\=\(string\)iso"
/GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstTypeFindElement:typefind.GstPad:src: caps = "NULL"
[New Thread 0x751b1470 (LWP 805)]
/GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstTypeFindElement:typefind.GstPad:src: caps = "video/quicktime\,\ variant\=\(string\)iso"

====== AIUR: 4.1.4 build on Jun 15 2017 12:17:10. ======
Core: MPEG4PARSER_06.12.07 build on May 16 2017 06:45:37
file: /usr/lib/imx-mm/parser/lib_mp4_parser_arm11_elinux.so.3.2

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x751b1470 (LWP 805)]
0x74995a48 in ?? () from /usr/lib/imx-mm/parser/lib_mp4_parser_arm11_elinux.so.3.2
(gdb) bt
#-1 0x74995a48 in ?? () from /usr/lib/imx-mm/parser/lib_mp4_parser_arm11_elinux.so.3.2
Backtrace stopped: Cannot access memory at address 0x2d2d2d24

(gdb)

The file B.m4A attached is intentionally not coherent for robustness testing purpose.

I have tried newer versions of imx-parser (4.1.5, 4.1.6 and 4.2.0) but this issue is still present.

Is there any way to prevent this SIGSEGV and make the parser exits with stream error?

Thanks for your help,

Labels (2)
0 Kudos
1 Reply

40 Views
joanxie
NXP TechSupport
NXP TechSupport

I uploded the lib file, could you test it?

0 Kudos