X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=STkytum4FvaOhs4N
	QBzvOUS/tOSP9afEltNnKLCVDEG7f/zgnAp8l6Fisy9OzMnEH/hKg8jKKPbtru76
	lPWZmyoERSlrsesoSMMcuODYQUOSUK6ILBZaQ6ohQD0kZmMbJlntlZL4I8drPNI/
	oRjAk0uEkVg2xAzrWkgy1rCcX8Q=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=QEqlv4MXj/3lYOZIKeJUxY
	6Qobk=; b=il0UFV1TkkM0/P7qL8RjHycoK+DkBAAX+xVYQJBkO8FIEe4qjfrVDD
	fpz57rsd67akjyrrbo6g1GzQf0b7S6qTy9QdjsTFZpuWpJQB94B+YBY742lda6J2
	69bBEm+u55AGYF/fCwvdD+d7MVYjoyyk2VquybV86IDFI2TBMAjLE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=relocated, captures, Hx-languages-length:1039, his
X-HELO: rgout0707.bt.lon5.cpcloud.co.uk
X-OWM-Source-IP: 31.51.205.159 (GB)
X-OWM-Env-Sender: jonturney AT btinternet DOT com
X-VadeSecure-score: verdict=clean score=0/300, class=clean
X-SNCR-VADESECURE: CLEAN
Subject: Re: An increment to Jon Turney's stackdump2backtrace script
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
References: <af84c3ce-364e-e058-ac39-ef2713e06cda AT maxrnd DOT com>
From: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID: <8541aec5-b9f1-c9c4-bdc6-2f5940d10bc2@dronecode.org.uk>
Date: Wed, 3 Oct 2018 18:08:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <af84c3ce-364e-e058-ac39-ef2713e06cda@maxrnd.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 01/10/2018 10:20, Mark Geisert wrote:
> For those Cygwin developers who tend to attract stackdump files...
> 
> ..mark (who defines an alias 'bt' to launch the script because he can't 
> get gdb out of his head)

Nice. Thanks.

> OTHERS=`ldd $IMG1 | awk '{print $3}' | sort -r | tr '\\n' ' '`

One thing you should be aware of here is that you are assuming that the 
other DLLs (i) have the same base address locally and on the system 
where the stackdump was generated [an assumption which rebase will tend 
to invalidate], and (ii) don't get relocated.

(The executable and cygwin1.dll don't suffer from this problem, as they 
have fixed addresses in the process memory layout used by cygwin)

For this reason, stackdumps are a weak tool for debugging crashes in 
other DLLs.  There were some patches posted to add DLL load addresses to 
the stackdump, not sure what happened to them...

It would perhaps be better to write a minidump, which captures that 
information (and more...)

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