Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Thu, 2 Jan 2003 10:23:56 +0000
From: "Steven O'Brien" <steven DOT obrien2 AT ntlworld DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Heads up: *possible* bug in cygwin
Message-Id: <20030102102356.659c336c.steven.obrien2@ntlworld.com>
In-Reply-To: <3E137C1C.50804@ece.gatech.edu>
References: <20030101100510 DOT 5b5b7f3f DOT steven DOT obrien2 AT ntlworld DOT com>
	<3E137C1C DOT 50804 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 01 Jan 2003 18:39:08 -0500
Charles Wilson <cwilson AT ece DOT gatech DOT edu> wrote:

> Steven O'Brien wrote:
> > My patch works around this problem by allocating a buffer of 1024
> > bytes for cygwin. I think I got this value by reading the cygwin dll
> > source to find a real upper bound, but it was a long time ago so
> > this needs checking. 
> 
> I saw this...it's probably a decent workaround, but hasn't yet been 
> accepted into current glib source AFAICT --- glib-2.2.0 still uses a
> 64 byte buffer for reading pw entries.  But that's not where the
> segfault is happening in my case (as my earlier message showed).

Just to be clear, I did not see any failure in this function either. But
failures later (in gnome-vfs I think) were due to memory corruption
which went away when I increased this buffer to 1024 bytes.
Circumstantial evidence I know, but I raised this issue just in case it
helps with glib-2.0.x. 

Steven


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/