From: "Andrew Fish" <afish@apple.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Turning on frame pointers
Date: Mon, 02 Nov 2020 12:05:27 -0800 [thread overview]
Message-ID: <DBA3821B-D232-46D3-9BAC-298A3E1EE903@apple.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
I just noticed a BZ [1] that requested the VS2019 turn on frame pointers. I happen to work a lot on a toolchain, Xcode, that has frame pointers enabled. So I’d figured I’d ask to see how interested folks are in this feature?
I’d like to point out it is just not a makes working with the debugger better kind of feature as it is useful to print out stack frames on ASSERT and exceptions.
For x86 you generally unwind the stack until you hit a zero. It is probably also a good idea for stack walker to skip guard pages, and non-canonical addresses so there is probably some set of PCDs that would useful in this regards.
[1] https://bugzilla.tianocore.org/show_bug.cgi?id=3043 <https://bugzilla.tianocore.org/show_bug.cgi?id=3043>
Thanks,
Andrew Fish
[-- Attachment #2: Type: text/html, Size: 1275 bytes --]
next reply other threads:[~2020-11-02 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 20:05 Andrew Fish [this message]
2020-11-04 5:22 ` 回复: [edk2-devel] Turning on frame pointers gaoliming
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-list 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=DBA3821B-D232-46D3-9BAC-298A3E1EE903@apple.com \
--to=devel@edk2.groups.io \
/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