Hi,
I'm using DVSDK 4_02 release on DM 368 The libraries are used to develop my video phone application is taken from this release. The encoder version given in dvsdk 4_2 release is I encountered with segmentation fault in Encoder. the bachtrace of the core dumps shows it in H264VENC_TI_ENCODE_FRAME_LITE. The following is the back trace of the dump
0 0x0008fcac in H264VENC_TI_Encode_Frame_Lite ()
#1 0x00083050 in H264VENC_TI_encode ()
#2 0x00025b40 in VIDENC1_process (handle=0x3125a8, inBufs=0x41338b10, outBufs=0x41338d50, inArgs=0x41338d44, outArgs=0x41338c7c) at videnc1.c:289
#3 0x00021658 in TIEncoder (psCamBuffInfo=<value optimized out>) at ./src/TI_dm368_Media.c:1602
#4 0x0001aa64 in DAMEncodeFrame (psCamBuffInfo=0x1901f0) at ./src/DAMVideoCodec.c:181
#5 0x0001acc0 in DAMEncoderThread () at ./src/DAMVideoCodec.c:69
This segment fault was observed nearly after 2 and a half hours. I've used the debug libraries i,,e h264venc_ti_arm926_debug.a provided in h264enc directory. I could not get the exact location of the segment fault. The parameters passed to VIDENC1_process () function is the same through out the call.
How can i solve this problem ?
