X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=rfMCJLnmzaNX++q6Wn5EbVx0CoRaCVAdBZhUU0TBNDHKORhmPPCuz
	d1weJRGSdFt2h6devbDjT2Sdk4MdScPNBOaXHH4KCMlumlhBtLqD6Ed4h2K2Fz9t
	cVkRZqkFqbU8juBewDS02OfAAd9mkEehfG+E3/6DIHPZl+Pr02+h9o=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=oNo10H24mjZWGyVJQPzHYBJ3Whs=; b=JND06tk66GJ9m9KaFmpuw+ueEqmZ
	e6h4BKdoDKYhtj3qGuVLcs5faRET7LYOFoHNkdhIAeWBVSdBQOvWBYVL2pAsnf78
	mdwB+MmMZzk0g6SWV3O7Hbnbp+TlcNHEeDCFk/cuJhLspSxLIU+hUV6KyL0TzLxg
	X1MZIUkhKLFJeeE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+8ahzmu7YoWNzAPho7Ecbo
Date:	Tue, 18 Mar 2014 15:32:18 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: sox - package is broken
Message-ID:	<20140318193218.GA4530@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20140310111427 DOT GE2828 AT calimero DOT vinschen DOT de> <5324E98D DOT 2090806 AT tiscali DOT co DOT uk> <20140316114332 DOT GB400 AT calimero DOT vinschen DOT de> <5326276F DOT 1050103 AT tiscali DOT co DOT uk> <20140317015736 DOT GA8086 AT ednor DOT casa DOT cgf DOT cx> <20140317022829 DOT GB8086 AT ednor DOT casa DOT cgf DOT cx> <20140317044230 DOT GA1235 AT ednor DOT casa DOT cgf DOT cx> <53278AE6 DOT 9040509 AT tiscali DOT co DOT uk> <20140318175353 DOT GA1051 AT ednor DOT casa DOT cgf DOT cx> <53289E8A DOT 1010601 AT tiscali DOT co DOT uk>
MIME-Version:	1.0
In-Reply-To:	<53289E8A.1010601@tiscali.co.uk>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Tue, Mar 18, 2014 at 07:29:14PM +0000, David Stacey wrote:
>On 18/03/2014 17:53, Christopher Faylor wrote:
>> On Mon, Mar 17, 2014 at 11:53:10PM +0000, David Stacey wrote:
>>> On 17/03/2014 04:42, Christopher Faylor wrote:
>>>> On Sun, Mar 16, 2014 at 10:28:29PM -0400, Christopher Faylor wrote:
>>>>> On Sun, Mar 16, 2014 at 09:57:36PM -0400, Christopher Faylor wrote:
>>>>>> On Sun, Mar 16, 2014 at 10:36:31PM +0000, David Stacey wrote:
>>>>>>> The issue I have is that close_audio_out() isn't working as you'd
>>>>>>> expect: for some reason, the 'audio_out_' member pointer is null
>>>>>> This was because all of the I/O operations were ignoring the archetype
>>>>>> for the device.  So, this is likely an old bug.
>>>>>>
>>>>>> So, good news/bad news.  Good news: I checked in a fix which causes the missing
>>>>>> 1.5 seconds to be played.  Bad news: The process now hangs in waveOutClose()
>>>>>> in fhandler_dev_dsp::Audio_out::stop.  There seem to be a few threads hanging
>>>>>> around waiting for something so obviously something isn't cleaning up right
>>>>>> in the audio code.
>>>>> Nope.  Wrong theory.  I know what's causing this but I don't yet know how to
>>>>> fix it.
>>>> This should all be fixed in the upcoming snapshot.
>>> Thank you for looking at this. I've tried the 32-bit snapshot dated
>>> '2014-03-17', but whenever I pipe a wav file to /dev/dsp I get a
>>> segmentation fault. The error is produced immediately, and no sound is
>>> heard. I've tried wav files both longer and shorter than 1.5s.
>> What does "pipe a wav file" mean?  I was testing this by doing:
>>
>> cp h.wav /dev/dsp
>
>I was testing with
>
>     cat ding.wav > /dev/dsp
>
>This gives a segmentation fault with the latest (2014-03-18) snapshot; 
>no sound is heard However, if I repeat your test:
>
>     cp ding.wav /dev/dsp
>
>Then that works and the ding dings. Which confuses me greatly - I've 
>been using *nix for nearly 20 years, and I honestly would have said that 
>the two lines above were synonymous - they're obviously not!

Ok.  I see a SEGV with "cat >".  Investigating.

FWIW, they are not the same.  There's lots of dup'ing going on under
the hood with "cat >".

cgf

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

- Raw text -