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: Fri, 17 Jan 2003 22:39:25 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: please try the latest snapshot
Message-ID: <20030118033925.GA20642@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20030117055216 DOT GA4969 AT redhat DOT com> <20030117154455 DOT GD2044 AT tishler DOT net> <20030117190353 DOT GA28900 AT redhat DOT com> <20030117194924 DOT GB1164 AT tishler DOT net> <20030117211727 DOT GC1164 AT tishler DOT net> <20030118010443 DOT GA1234 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030118010443.GA1234@redhat.com>
User-Agent: Mutt/1.5.1i

On Fri, Jan 17, 2003 at 08:04:43PM -0500, Christopher Faylor wrote:
>On Fri, Jan 17, 2003 at 04:17:27PM -0500, Jason Tishler wrote:
>>Chris,
>>
>>On Fri, Jan 17, 2003 at 02:49:24PM -0500, Jason Tishler wrote:
>>> On Fri, Jan 17, 2003 at 02:03:53PM -0500, Christopher Faylor wrote:
>>> > This should be fixed now.  It was a simple mistake, as far as I
>>> > could tell.  How does the refreshed snapshot look?
>>> 
>>> Looking good!
>>
>>I spoke too soon.  I'm getting segmentation faults and stuff like the
>>following by just running ls:
>>
>>    $ uname -a
>>    CYGWIN_NT-5.0 TISHLERJASON 1.3.19s(0.71/3/2) 20030117 13:11:17 i686 unknown
>>    $ cd src/pgsql
>>    /home/jt/src/pgsql
>>    $ ls
>>    ...
>>     636511 [unknown (0x900)] ? 2332 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
>>     636647 [unknown (0x900)] ? 2332 handle_exceptions: Error while dumping state (probably corrupted stack)
>
>Could you get a gdb backtrace of this problem?

Nevermind.  I cd'ed around my disk like crazy until I could duplicate the
problem.  I'm regenerating the snapshot now.

If it has this in the ChangeLog:

2003-01-17  Christopher Faylor  <cgf AT redhat DOT com>

	* cygheap.cc: Change most 'int's to 'unsigned's.
	(_cmalloc): Only check for size of malloced region when calculating
	budget.  Add overhead when performing the sbrk.  Previous change broke
	_crealloc.

It should work.


cgf

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