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=m3xv7rSBER7enkz9oYaHJm96F5Z/9IpOPvxb3E/jbP8VTij6JyHoU ak2eVaIBIrLshvwsf6Pc1kNrUw4mwVZHqqxumvMhSc7Qk24gvz3UEd14H2Ak9plk /M19I/bhoeA81XlPMWNmzqCnJULrsHL1ghJbUZ0VIcC3cfmdX8ppQ0= 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=y6mlRU86EQgxRXjLcVCD1XyZU+8=; b=yonG0MzX1CJ5KyY2TjL5wdLVPIwW Ja2ukA+oSWfjeV4jmWxNGeN38MFD+80y8O/fcRXlxp9djELZnjgv7TAr22Ce9TTp 1RpV2AsGQP/RDrXuMPv8bCax4g5dMTi+9KDVF7BTfBIYL5Hq7c2iQZMoe+bCXavG OsBkXwH8ioZOK/8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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: U2FsdGVkX19wOIrlf138pPNcjz+d9D/1 Date: Tue, 18 Mar 2014 20:55:12 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: sox - package is broken Message-ID: <20140319005512.GB6466@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <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> <1395190188105-107200 DOT post AT n5 DOT nabble DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1395190188105-107200.post@n5.nabble.com> User-Agent: Mutt/1.5.20 (2009-06-14) On Tue, Mar 18, 2014 at 05:49:48PM -0700, PolarStorm wrote: >David Stacey wrote >> 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! > >Two things I can think of: > >1) With "cat" the output file is created/handled by the shell, whereas "cp" >is doing its own file creation. You should see what's going on by: > strace cat ding.wav > /dev/dsp > strace cp ding.wav /dev/dsp > >2) Cat is trying to expand sparse files and perhaps it thinks of your >ding.wav as containing sparse data? > >Also, I would guess, that the dsp driver should handle bit streamed input >differently than a block copy/dump? Actually it was the improper passing of /dev/dsp file data to an execed process that was the problem. 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