This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Segmentation Fault after VIDENC1_process call

Hi

i get segmentation fault error some times with DM368 using H264 Platinum Codec, chain mode.

while i debuged it the error is coming for strncmp()

the gdb debugg flow is

1.encode (this=0x3b2e70, pInBuffer=0x382340, pOutBuffer=0x0)
2.VIDENC1_process ()
3.H264VENC_TI_encode ()
4.HDVICPSYNC_start (handle=0x49792000, intType=HDVICPSYNC_IRQ, hdvicpHandle=0x4b018000) at hdvicpsync.c:67
5._GT_create ()

6.getModNameFlagsAddr ()

7.findElem ()
8.strncmp () from /nfsroot/snb5000/lib/libc.so.6

---------------------------------

[Switching to Thread 658]
0x4035a980 in strncmp () from /home/megaking/Dev/camera/nfsroot/snb5000/lib/libc.so.6
(gdb) bt
#0  0x4035a980 in strncmp () from /home/megaking/Dev/camera/nfsroot/snb5000/lib/libc.so.6
#1  0x002c003c in findElem ()
#2  0x002c0064 in getModNameFlagsAddr ()
#3  0x002c0550 in _GT_create ()
#4  0x002ba1c0 in HDVICPSYNC_start (handle=0x49792000, intType=HDVICPSYNC_IRQ, hdvicpHandle=0x4b018000) at hdvicpsync.c:67
#5  0x0029f918 in H264VENC_TI_encode ()
#6  0x002307c4 in VIDENC1_process ()
#7  0x0020c774 in Dm365VideoH264Encoder::encode (this=0x3b2e70, pInBuffer=0x382340, pOutBuffer=0x0)
    at camera/Dm365VideoH264Encoder.cpp:863
#8  0x0020b890 in virtual thunk to Dm365VideoH264Encoder::encode(_Buffer_Object*, _Buffer_Object*) ()
    at camera/Dm365VideoH264Encoder.cpp:1327
#9  0x00202484 in Dm365VideoEncoder::mainLoop (this=0x383468) at camera/Dm365VideoEncoder.cpp:703
#10 0x001749dc in Thread::threadFunc (arg=0x383468) at scheduler/Thread.cpp:91
#11 0x4002a8f8 in ?? () from /home/megaking/Dev/camera/nfsroot/snb5000/lib/libpthread.so.0
Cannot access memory at address 0x0
#12 0x4002a8f8 in ?? () from /home/megaking/Dev/camera/nfsroot/snb5000/lib/libpthread.so.0
Cannot access memory at address 0x0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

----------------------------------