Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 20:04:43 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: please try the latest snapshot Message-ID: <20030118010443.GA1234@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030117211727.GC1164@tishler.net> User-Agent: Mutt/1.5.1i 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? 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/