public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Vladimir Olovyannikov" <vladimir.olovyannikov@broadcom.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: devel@edk2.groups.io
Subject: Debugging aarch64 edk2 built with gcc-8.x 64-bit arm compiler
Date: Fri, 6 Dec 2019 15:50:47 -0800	[thread overview]
Message-ID: <102e9863f7b0a90cbf854d059d9bcf25@mail.gmail.com> (raw)

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

Hi Ard,



We are about to switch to the latest Yocto. It is shipped with gcc-8.3
aarch64-linux-gnu compiler.

We use DS5 for bare metal debugging.

When I build edk2 with gcc-7-x/gcc-8.x, DS5 complains on DWARF format.
I tried to explicitly set it to DWARF2, but still cannot even get the stack
or local variables (even though DS5 does not complain),
even for edk2 NOOPT build.



Using gcc-6.3 from Linaro, I don’t see any issue with DS5 debugging.

Am I missing any steps?

Build is done with GCC5_AARCH64_PREFIX=aarch64-linux-gnu



Another question: it seems that the DS5 scripts limit the path size with
255 chars. With a source built by Yocto, it can easily be more than that.

Attempt to add symbols for such modules ends up with error message in the
DS5 command window that it could not add those symbols.

Is there a procedure to increase the path length limit?



Thank you,
Vladimir

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

             reply	other threads:[~2019-12-06 23:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 23:50 Vladimir Olovyannikov [this message]
2019-12-10 17:13 ` Debugging aarch64 edk2 built with gcc-8.x 64-bit arm compiler Ard Biesheuvel
2019-12-10 17:25   ` Vladimir Olovyannikov
2019-12-11 14:51     ` Ard Biesheuvel
2019-12-12 16:07       ` Sami Mujawar
2019-12-12 17:51         ` Vladimir Olovyannikov
2019-12-12 18:32           ` Sami Mujawar
2019-12-12 18:56             ` Vladimir Olovyannikov

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=102e9863f7b0a90cbf854d059d9bcf25@mail.gmail.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