Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Mon, 7 Jun 2004 11:15:46 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.5.9.1: MPEG2 SSG mpeg2v12 reports "zero file size"
Message-ID: <20040607151546.GA15531@coe.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <002701c44c9e$f5ddbcf0$5473cd89@fvuvpgkv5i> <6.1.0.6.0.20040607105743.03200820@pop.prospeed.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.1.0.6.0.20040607105743.03200820@pop.prospeed.net>
User-Agent: Mutt/1.4.1i

On Mon, Jun 07, 2004 at 11:01:44AM -0400, Larry Hall wrote:
>At 06:02 AM 6/7/2004, you wrote:
>>The mpeg2 codec (mpeg2v12 from MPEG2 SSG
>>http://www.mpeg.org/MPEG/MSSG/#source used to work fine on cygwin 1.5.5
>>.  But when I upgrade to cygwin1.dll 1.5.9.1, the program always report
>>something like "zero file size".
>>
>>After spending a lot of time tracing the source, I found that it goes
>>wrong when it rewind the video bitstream the 3rd time in main().  If I
>>fix the rewind problem, things go wrong in other part of the program.
>>
>>Since it works well in 1.5.5, I wonder there's something wrong with
>>cygwin kernel.  Could anybody tell me why or how to fix the problem on
>>newer kernels?
>
>
>You mean beyond the obvious course of action (i.e.  debugging)?  Well,
>I'd recommend checking 1.5.10 since it's the current release.  If that
>doesn't resolve the issue, I suppose you could try a snapshot to see if
>the problem has been caught and resolved after the release (though you
>may see other problems since snapshots at this point are the result of
>active and ongoing development, with very little testing).  Otherwise,
>your best bet is to build the Cygwin DLL and debug into it as needed.

And, there's always the "old reliable" http://cygwin.com/problems.html .

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

