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=SLT6vBgw10LC/IOc sGBu4xXcIf6pvOwUG5z2MgXzUbhmTTzDQuTKk+/P0fSVvIDfNaw+3Zhb9iY5J4dW 6Dv/ta6TZr9N5M/MRvAdzSL6pv/YeJA9hojQQVNPVZVm9qPIdhi/MDm7hfY4FEa8 s/ZPrbAgX8A0Hqr/Gx0P0L1zu/Y= 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=zJFYI85Ua1BP9/uYfbRWmb 8B7Is=; b=sy+dnkmKkTFbT/63j/hg+31WAFmpNhHEL9Kgp4Ry+0dezmYniRPAS6 3xLJzPqTebMf+4gmKxWxPj5hayT4ozb6S7Ch12Q+Z/OsUv4ZI2Y96Ouqxlj+XQ5U 1WZxScZMpQ9NAUVtYwuqfqc5vgIswKo9KMWsFEhzxk1TTaUDmdAJs= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=0.5 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*UA:Firefox, toward, Turney, turney X-HELO: m0.truegem.net Subject: Re: An increment to Jon Turney's stackdump2backtrace script To: cygwin AT cygwin DOT com References: <8541aec5-b9f1-c9c4-bdc6-2f5940d10bc2 AT dronecode DOT org DOT uk> From: Mark Geisert Message-ID: <8ff3264e-eb21-25f7-6a45-76b7309738f7@maxrnd.com> Date: Thu, 4 Oct 2018 02:18:02 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: <8541aec5-b9f1-c9c4-bdc6-2f5940d10bc2@dronecode.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Jon Turney wrote: > 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. True. It's geared toward my workflow which only deals with stuff I've built on my own machine and debugging/fixing pretty soon after causing the stackdump. Any update to any of the files involved risks invalidating the stackdump. > (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... Huh. I'll see if I can find them in the cygwin-patches archive. > It would perhaps be better to write a minidump, which captures that information > (and more...) Are you alluding specifically to Windows minidump or just generally a small information dump? On a related topic, I noticed dumper.exe in winsup/utils and played around with it. I'm unsure if it captures everything one would want in a corefile. I'm also unsure if there could even be a PE/COFF corefile and what it would contain. Cheers, ..mark -- 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