[Live-devel] Segfault in FileSink while indexing MPEG2-TS

[Rutherford, Robert]

Ross,

It seems to be a problem with stack overflow.  In our application we
create each task with a stack size of 32k (which seems like plenty),
however, when I increased the stack of the task that runs the indexer
code to 128k, it works without error (testing on the ~180MB file).
However, we need to be able to use this on a 2GB file, which we are
unable to test at the time.  I am worried that 128k may not be enough
for a larger file.  My best guess is that the stack overflow is caused
by recursive function calls.  Do  you recall anything in the design that
could cause several recursive function calls without returning?


Date: Thu, 19 Apr 2007 15:38:11 -0700
From: Ross Finlayson <finlayson at live555.com>
Subject: Re: [Live-devel] Segfault in FileSink while indexing MPEG2-TS
To: LIVE555 Streaming Media - development & use
	<live-devel at ns.live555.com>
Message-ID: <f0624080ac24d9f7768df@[66.80.62.44]>
Content-Type: text/plain; charset="us-ascii"

>I am working to integrate the MPEG2-TS file indexer in to an 
>existing application by basically using the same method as 
>MPEG2TransportStreamIndexer.cpp within a function.  However, the 
>application crashes with a segmentation fault after writing 880-924 
>bytes or so of the index file (from a transport stream of 
>approximately 180 MB).  When I compile and run 
>MPEG2TransportStreamIndexer as a stand-alone binary it works 
>correctly on the same MPEG file.  I need to use it within the 
>application in order to better catch error values and prevent 
>unneeded system calls.  Has anyone else seen this problem, or is 
>there a known issue in this release?

No, there's no known problem.  However, because the indexing code 
works OK in the supplied "MPEG2TransportStreamIndexer" application, 
but not when you modify it, you should be able to track down the 
problem without too much difficulty, I hope.
-- 

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.live555.com/pipermail/live-devel/attachments/20070419/d03fd
e50/attachment-0001.html