public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Nielsen <a.nielsen@shikadi.net>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] dvbstream reliability issues?
Date: Fri, 21 Mar 2008 10:54:13 +1000	[thread overview]
Message-ID: <47E30735.1020604@shikadi.net> (raw)
In-Reply-To: <200803201002.47240.Nicola.Sabbi@poste.it>

> I use it for hours, even forgetting that it's recording, without 
> segfaults.
> Try to run it under gdb (after having compiled it with -g) and 
> see with "bt" where it segfaults, or bugs can't be fixed

What's your reception like?  This particular card (DVico Fusion HDTV)
seems to be somewhat less sensitive compared to my other cards, and I
think getting corrupted data coming in is what breaks dvbstream.  The
recording itself is full of blips as if the reception is quite bad.

When the recording just stops (no crash) gdb doesn't seem to reveal
anything amazing:

<Ctrl+C>
Program received signal SIGINT, Interrupt.
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7ebf77b in poll () from /lib/libc.so.6
#2  0x0804aeeb in main (argc=12, argv=0xbfe38484) at dvbstream.c:1516
(gdb) fr 2
#2  0x0804aeeb in main (argc=12, argv=0xbfe38484) at dvbstream.c:1516
1516            poll(pfds,1,500);
(gdb) cont
Continuing.
[Still no DVB data being written to disk]
<Ctrl+C>
Program received signal SIGINT, Interrupt.
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7ebf77b in poll () from /lib/libc.so.6
#2  0x0804aeeb in main (argc=12, argv=0xbfe38484) at dvbstream.c:1516
(gdb) fr 2
#2  0x0804aeeb in main (argc=12, argv=0xbfe38484) at dvbstream.c:1516
1516            poll(pfds,1,500);


If I kill dvbstream and reload it then all is fine, so it seems that
maybe the card loses sync with the signal, and either dvbstream needs to
retune the card, or perhaps the kernel driver should do that automatically.

When it crashes it looks like this:


Program received signal SIGSEGV, Segmentation fault.
0xb7ee153c in memcpy () from /lib/libc.so.6
(gdb) bt
#0  0xb7ee153c in memcpy () from /lib/libc.so.6
#1  0x08049714 in collect_section (section=0x815bef0, pusi=<value
     optimized out>, buf=0x3ffff59e <Address 0x3ffff59e out of bounds>,
     len=3221135360) at dvbstream.c:579
#2  0x0804b21b in main (argc=12, argv=0xbffe8084) at dvbstream.c:683

(gdb) fr 1
#1  0x08049714 in collect_section (section=0x815bef0, pusi=<value
     optimized out>, buf=0x3ffff59e <Address 0x3ffff59e out of bounds>,
     len=3221135360) at dvbstream.c:579
579       memcpy(&(section->buf[section->pos]), buf, len);

(gdb) fr 2
#2  0x0804b21b in main (argc=12, argv=0xbffe8084) at dvbstream.c:683
683       skip = collect_section(&(pmt->section), pusi, b, l);


It looks like the default CFLAGS do some optimisation - let me know if
you need me to recompile it without this.

Cheers,
Adam.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-03-21  0:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  8:57 [linux-dvb] dvbstream reliability issues? Adam Nielsen
2008-03-20  9:02 ` Nico Sabbi
2008-03-21  0:54   ` Adam Nielsen [this message]
2008-03-21  8:52     ` Nico Sabbi
2008-03-24 18:35       ` Nico Sabbi
2008-03-24 23:23         ` Adam Nielsen
2008-03-29  9:25         ` Nico Sabbi
2008-03-29 11:33           ` Adam Nielsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47E30735.1020604@shikadi.net \
    --to=a.nielsen@shikadi.net \
    --cc=linux-dvb@linuxtv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox