Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Wed, 9 Jan 2002 12:54:44 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Cc: Norman Vine Subject: Re: PostgreSQL and CVS DLL Message-ID: <20020109175444.GC5582@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com, Norman Vine References: <20020109162551 DOT GE1672 AT dothill DOT com> <016501c1992c$45ef3580$a300a8c0 AT nhv> <20020109170121 DOT GH1672 AT dothill DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020109170121.GH1672@dothill.com> User-Agent: Mutt/1.3.23.1i On Wed, Jan 09, 2002 at 12:01:21PM -0500, Jason Tishler wrote: >Norman, > >On Wed, Jan 09, 2002 at 11:39:56AM -0500, Norman Vine wrote: >> OK -- using snapshots from cygwin.com >> >> postgres runs fine using snapshot DLL dated 20011231 >> crashes for me with all DLL's dated 20020104 and later >> >> I have a locally built DLL 20020103 that also crashes > >Please try to determine what specific Cygwin change is causing the >postmaster problem. Since the date range is small, searching cygwin-cvs >should not take too long. Where is the analysis of *where* the program died? That should be pretty simple to show. Look at how-to-debug-cygwin.txt for details. Let me make this level of analysis a prerequisite for future bug reports here. For extra points, a gdb backtrace will also help track down the problem. Look at what Jonathan Kamens does to try to track down a problem. That would be wonderful. For even more points, an actual patch would really make my day. cgf