From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: An increment to Jon Turney's stackdump2backtrace script
Date: Wed, 03 Oct 2018 17:08:00 -0000 [thread overview]
Message-ID: <8541aec5-b9f1-c9c4-bdc6-2f5940d10bc2@dronecode.org.uk> (raw)
In-Reply-To: <af84c3ce-364e-e058-ac39-ef2713e06cda@maxrnd.com>
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
next prev parent reply other threads:[~2018-10-03 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 9:21 Mark Geisert
2018-10-03 17:08 ` Jon Turney [this message]
2018-10-04 9:18 ` Mark Geisert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8541aec5-b9f1-c9c4-bdc6-2f5940d10bc2@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).