Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<39216349.7FD345EA@camline.com>
Date:	Tue, 16 May 2000 17:03:37 +0200
From:	Johannes =?iso-8859-1?Q?M=E4hner?= <johanm AT camline DOT com>
Organization:	camline
X-Mailer:	Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language:	en
MIME-Version:	1.0
To:	earnie_boyd AT yahoo DOT com
CC:	cygwin users <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: zsh and status access violation
References:	<20000516140807 DOT 7418 DOT qmail AT web122 DOT yahoomail DOT com>

Earnie Boyd wrote:
> You'll have to look at the values of synch[0] and dummy.  My guess is that
> dummy has a 0x0 value which means that your trying to access an invalid memory
> location.  You'll then have to determine why it has the value 0x0 and either
> resolve that or condition the read so that it is called only if dummy has a
> value.

-- sync is two-int array with filedescriptors 
(filled by a pipe statement: "pipe(synch);")
sync[0] = 3
sync[1] = 4


-- dummy is a function-local variable, 
defined as "char dummy;" (one-byte-buffer)

Allocating heap memory instead of using this local-one-byte-buffer
yields the same symptoms.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -