public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <afish@apple.com>
Subject: 回复: [edk2-devel] Turning on frame pointers
Date: Wed, 4 Nov 2020 13:22:06 +0800	[thread overview]
Message-ID: <004801d6b26a$701f8640$505e92c0$@byosoft.com.cn> (raw)
In-Reply-To: <DBA3821B-D232-46D3-9BAC-298A3E1EE903@apple.com>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

Andrew:

 Do you notice how much the image size will be increased when frame pointer is enabled?

 

Thanks

Liming

发件人: bounce+27952+66878+4905953+8761045@groups.io <bounce+27952+66878+4905953+8761045@groups.io> 代表 Andrew Fish via groups.io
发送时间: 2020年11月3日 4:05
收件人: edk2-devel-groups-io <devel@edk2.groups.io>
主题: [edk2-devel] Turning on frame pointers

 

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

 

Thanks,

 

Andrew Fish




[-- Attachment #2: Type: text/html, Size: 5235 bytes --]

      reply	other threads:[~2020-11-04  5:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 20:05 Turning on frame pointers Andrew Fish
2020-11-04  5:22 ` gaoliming [this message]

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='004801d6b26a$701f8640$505e92c0$@byosoft.com.cn' \
    --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