Question, do all packets have CRCs? Is it possible a packet simply doesn't have one?<br><br>- Mark.<br><br><div><span class="gmail_quote">On 4/12/06, <b class="gmail_sendername">Daniel Kristjansson</b> <<a href="mailto:danielk@cuymedia.net">
danielk@cuymedia.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Wed, 2006-04-12 at 16:23 -0400, Mark Buechler wrote:
<br>> Daniel, I don't wish to bug, but I was wondering if you had a few<br>> minutes to look at this one. I'm sure it's something simple but I<br>> don't know enough about TS packets to really know what I'm looking at.
<br><br>Ok, so since we are in the "if (is_start)" portion handle_packet()<br>it looks like this is the first TS packet of a PES packet.<br><br>Then it looks like the length of the adaptation field is zero<br>since len == 0. This is the case for most PES packets.
<br><br>Then it looks like we call write_section_data() with<br>a length of "p_end - p" which in this case is 183 bytes,<br>this again is normal.<br><br>So it looks like the problem is somewhere within the write_section_data
<br>function.<br><br>Anyway, it looks like section_h_size is 37 when it crashed, which is<br>a bit on the short side, even for a PAT packet. Is this happening<br>on the first trip through the "while (1)" loop, or has some bad data
<br>gotten in there (it looks like the first time, since section_index<br>hasn't been shrunk from the original 183). Was the CRC checked?<br>It looks like we keep trying to parse the packet even if the CRC<br>fails, which seems wrong to me; though in truth it shouldn't cause
<br>a segfault since section_index always gets shrunk when we copy<br>the data.<br><br>I hope this helps, I recommend printing out the section_index<br>and section_h_size before you enter the loop, and then printing<br>the results of each step of the parsing in the loop. Then wait
<br>for a segfault and then look at the last lines of the log.<br><br>-- Daniel<br><br><br>_______________________________________________<br>mythtv-dev mailing list<br><a href="mailto:mythtv-dev@mythtv.org">mythtv-dev@mythtv.org
</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</a><br></blockquote></div><br>