| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-SWARE-Spam-Status: | No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,TW_YG |
| X-Spam-Check-By: | sourceware.org |
| X-Mail-Handler: | Dyn Standard SMTP by Dyn |
| X-Report-Abuse-To: | abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) |
| X-MHO-User: | U2FsdGVkX19+aRpagLE9XULgPBkdKm/Y |
| Date: | Mon, 18 Feb 2013 10:46:43 -0500 |
| From: | Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: psql crashes with snapshot |
| Message-ID: | <20130218154643.GB2682@ednor.casa.cgf.cx> |
| Reply-To: | cygwin AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| References: | <kfth8i$8bm$1 AT ger DOT gmane DOT org> |
| MIME-Version: | 1.0 |
| In-Reply-To: | <kfth8i$8bm$1@ger.gmane.org> |
| User-Agent: | Mutt/1.5.20 (2009-06-14) |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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 |
On Mon, Feb 18, 2013 at 04:27:17PM +0100, Thorsten Kampe wrote: >Hello, > >I just downloaded the PostgreSQL client tools and noticed that psql >crashes every time. The usual rebase didn't help. I reverted cygwin1.dll >to the latest official version (1.7.17, 2012-10-19) and now psql works >fine. > >What can I do - if anything at all - to debug the issue? Obviously, I >cannot test every single snapshot after October last year and see where >the crash "starts"... It isn't clear why you couldn't do that but you could at least provide *details* like cygcheck output and what you mean by "crash". If there is a stackdump file then posting that would be useful. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |