Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 17 May 2000 22:54:18 -0400
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: The "new" stack trace format
Message-ID: <20000517225418.A7677@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i

As you probably all know, DJ implemented a new stack trace format for
cygwin several months ago.

I just wanted to express my appreciation for this new format as it helped
me track down a problem that I was having which was hard to reproduce
when running under gdb.

The layout is a lot easier to visually decode than the previous version
and I realized that after looking at five or six stackdumps.

Of course, I thought there was a problem with the code that was walking
the stack since the same addresses seemed to be repeating in the "Function"
column but, of course, duh, the problem was that one of cygwin's functions
was being called recursively, erroneously.

cgf