www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-0.3 required=5.0 tests=BAYES_00,FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <22994946.post@talk.nabble.com> |
Date: | Fri, 10 Apr 2009 14:28:49 -0700 (PDT) |
From: | Tarmik <tapika AT yahoo DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: seg fault produces stackdump with no stack trace |
In-Reply-To: | <20080801191550.GA18883@ednor.casa.cgf.cx> |
MIME-Version: | 1.0 |
References: | <loom DOT 20080801T151340-446 AT post DOT gmane DOT org> <loom DOT 20080801T174446-165 AT post DOT gmane DOT org> <20080801191550 DOT GA18883 AT ednor DOT casa DOT cgf DOT cx> |
X-IsSubscribed: | yes |
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 |
> I just checked in a fix which should keep the stack trace going even > when it finds a return address of zero. > It will be in the next cygwin snapshot at: http://cygwin.com/snapshots/ > but be advised that this is a 1.7.x version of Cygwin and there ar > changes to the way mounts are handled in this new version as well as > other incompatibilies with the current stable 1.5.x series. So, if > you use it, please research the differences by reading the cygwin > mailing list archives. I have similar problem , and I would like to get fix for this. However - I have latest stable cygwin1.dll as v1.5, and trying to replace it with v1.7 produces more problems. Would it be possible to tell me what needs to be changed and where - may be we could try to patch v1.5 only with that backtrace support, no other changes ? Or do I somehow upgrade whol cygwin ? -- View this message in context: http://www.nabble.com/seg-fault-produces-stackdump-with-no-stack-trace-tp18777069p22994946.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |