DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=Ey2
	JdAfXEx6TcJxxDKGFlDYcl6hjJ03VoO+9Q4+hchvYrQJEs8+p0L4/COxpjz5gKcg
	6ikF5/BuWeeikKbqIZdzW2SAMd/GB6sW/OoA/Uxes/Z4fFSqidrhF1h9j8Ouq9V+
	DzZtq1AcRO1tAW85aipxznmhpLGomoxZC3VA9VFI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: "michele.sanges" <michele.sanges@gmail.com>
Subject: Error writing to /dev/dsp.
Date: Tue, 14 May 2013 17:22:31 +0200 (CEST)
Lines: 28
Message-ID: <kmtkrj$vlj$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi all,
I wish report a problem regarding the use of  /dev/dsp device.

My program opens this device, then configures and writes a data
 stream in it.

The write operation is made passing to the write() function a
 valid /dev/dsp file descriptor, as returned from the open
 function, the buffer data and its lenght.

With the latest cygwin release (1.7.18-1), the write function
 crashes (segmentation fault) or doesn't return at
 all.

With an old version (year 2011) it works without problems.

Does someone has encountered this behavior?

Within the cygwin 1.7.11-1 revision log I can read that it
 resolves a write problem to the /dev/dsp device.

Can be the same problem I reported?

Thanks.


-- 


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