From: Ron Gage <ron@rongage.org>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] crash issue with dvbstream
Date: Fri, 07 Nov 2008 22:43:45 -0500 [thread overview]
Message-ID: <49150AF1.5060601@rongage.org> (raw)
I am having problems with dvbstream segfaulting. The segfaults are
occurring at line 635 of dvbstream.c - PAT.entries[] are basically NULL
causing the segfault.
I was asked by mrec on the IRC channel to make a ts dump of the video
signal I am trying to stream. That stream is at
http://www.mi-connect.com/crash.ts. This dump file is roughly 224 meg
in size.
Let me know if I can help in finding this problem.
Ron Gage
Westland, MI
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next reply other threads:[~2008-11-08 3:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 3:43 Ron Gage [this message]
2008-11-08 9:03 ` [linux-dvb] HVR 1400 djamil
2008-11-08 9:06 ` djamil
2008-11-08 10:31 ` djamil
2008-11-08 16:40 ` djamil
2008-11-08 19:35 ` djamil
2008-11-09 0:17 ` CityK
[not found] ` <1226213780.8564.1.camel@toptop>
2008-11-09 20:50 ` [linux-dvb] [Bulk] " CityK
2008-11-09 6:36 ` [linux-dvb] " djamil
2008-11-08 13:53 ` [linux-dvb] crash issue with dvbstream Nico Sabbi
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=49150AF1.5060601@rongage.org \
--to=ron@rongage.org \
--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