#2110 closed defect (wontfix)
OSCAM Crash (seems related when DNS Reader was not answer)
Reported by: | Sebastiii | Owned by: | kpc |
---|---|---|---|
Priority: | blocker | Component: | Protocol - CCCam |
Severity: | high | Keywords: | DYNDNS CCCam Reader crash |
Cc: | Sensitive: | no |
Description
Revision
5893 but older too (seems 1.1.0 is working)
Issue Description
I have 2 readers xxx.dyndns.org and xxx2.dyndns.org wher no answer on Port 12000.
After a while OSCAM closed Itself, tested on Dreambox (Enigma2) and Ubuntu
When the issue occurs
After 5 to 20 minutes
How the issue is reproducable
Set DYNDNS Reader (CCcam) when ping we have the latest Adress IP but not answering and not answering on port 12000.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7fa3b70 (LWP 9747)]
0x0014033d in pthread_mutex_lock () from /lib/i386-linux-gnu/libpthread.so.0
(gdb) bt
#0 0x0014033d in pthread_mutex_lock ()
from /lib/i386-linux-gnu/libpthread.so.0
#1 0x0805460a in add_job (cl=0xa3e7262, action=24 '\030', ptr=0x8248828,
len=96) at /usr/local/bin/oscam-svn/oscam.c:3155
#2 0x0804fe29 in write_ecm_answer (reader=0x8199020, er=0x8342848,
rc=4 '\004', rcEx=39 '\, cw=0x0, msglog=0x0)
at /usr/local/bin/oscam-svn/oscam.c:1719
#3 0x08094ffd in cc_send_ecm (cl=0x8201e70, er=0x83333b0,
buf=0xb7fa2b6c "\021)\b\b\244z\030\b\261\215/")
at /usr/local/bin/oscam-svn/module-cccam.c:1037
#4 0x08087217 in casc_process_ecm (reader=0x8199020, er=0x8342848)
at /usr/local/bin/oscam-svn/oscam-reader.c:380
#5 0x08087696 in reader_get_ecm (reader=0x8199020, er=0x8342848)
at /usr/local/bin/oscam-svn/oscam-reader.c:438
#6 0x080540c5 in work_thread (ptr=0x831ac40)
at /usr/local/bin/oscam-svn/oscam.c:3051
#7 0x0013de99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8 0x0036d73e in clone () from /lib/i386-linux-gnu/libc.so.6
Change History (4)
comment:1 by , 13 years ago
Owner: | set to |
---|
comment:2 by , 13 years ago
Owner: | changed from | to
---|
comment:3 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
seg fault is one of the most useful log for devs, thanks for posting but maybe it's better to keep all in one thread in fourm instead of tickets. please post your furthure seg fault log here (as i quote your log here :
http://www.streamboard.tv/wbb2/thread.php?postid=391242#post39124
Cu