Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.1.0.6.0.20040607111707.031fdbc8@pop.prospeed.net>
X-Sender: 
Date: Mon, 07 Jun 2004 11:17:59 -0400
To: cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: 1.5.9.1: MPEG2 SSG mpeg2v12 reports "zero file size"
In-Reply-To: <20040607151546.GA15531@coe.casa.cgf.cx>
References: <002701c44c9e$f5ddbcf0$5473cd89 AT fvuvpgkv5i> <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040607105743 DOT 03200820 AT pop DOT prospeed DOT net> <20040607151546 DOT GA15531 AT coe DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:15 AM 6/7/2004, you wrote:
>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 .


Oh *that*.  Nobody uses that anymore. ;-)


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/