Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<009601c0d8d9$0647b740$7f291518@CX535256E>
From:	"Barubary" <barubary AT home DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	Cygwin and Winamp, part 2
Date:	Wed, 9 May 2001 15:40:18 -0700
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400

Never mind that last email.  It's still broken.  I think it's actually the
fork() mechanism that is screwing up my machine.  When a cygwin application
loads, while Winamp is playing a song, Winamp freezes its playback.

There are many other side effects.

The instruction at "0x61037F94" referenced memory at "0x00000000".  The
memory could not be "written".

I get that when closing some programs; always when I close man, and every so
often when a "make" finishes (usually this occurs when many makes are done,
like nested makes)

-- Barubary


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -