Re: Debugging aarch64 edk2 built with gcc-8.x 64-bit arm compiler

["Ard Biesheuvel" <ard.biesheuvel@linaro.org>]

On Tue, 10 Dec 2019 at 18:25, Vladimir Olovyannikov
<vladimir.olovyannikov@broadcom.com> wrote:
>
> > -----Original Message-----
> > From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Sent: Tuesday, December 10, 2019 9:13 AM
> > To: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>; Sami
> > Mujawar <Sami.Mujawar@arm.com>
> > Cc: edk2-devel-groups-io <devel@edk2.groups.io>
> > Subject: Re: Debugging aarch64 edk2 built with gcc-8.x 64-bit arm compiler
> >
> > On Sat, 7 Dec 2019 at 00:50, Vladimir Olovyannikov
> > <vladimir.olovyannikov@broadcom.com> wrote:
> > >
> > > 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?
> > >
> >
> > I have never in my life used a DS-5 to debug EDK2 running on bare metal,
> > so
> > unfortunately, I won't be able to help you.
> >
> How do you normally debug edk2 with DS5? Or, are you using a different
> mechanism?
> Debugging with DS5 was/is very convenient.
>

I do my prototyping mainly in QEMU, using GDB for debug.