X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Fri, 10 Apr 2009 21:34:33 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: seg fault produces stackdump with no stack trace
Message-ID: <20090411013433.GA8974@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <22994946 DOT post AT talk DOT nabble DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <22994946.post@talk.nabble.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Fri, Apr 10, 2009 at 02:28:49PM -0700, Tarmik wrote:
>>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 ?

You have to *research the differences* as mentioned in the seven month
old email that you are quoting.

But the good news is that it is easier to research now.  Just read what's
written on the home page at http://cygwin.com/ .

cgf

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