public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: david moheban <moheban79@gmail.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: WARNING: No source level debug
Date: Fri, 08 Sep 2017 17:33:09 +0000	[thread overview]
Message-ID: <CADxnD1yyZuNo9hD0pA8_NEvOV2ngr2acmFDCNV2XrKwO+xPUHg@mail.gmail.com> (raw)

I checked all of the DebugLib instances and I believe they are all there
though in different locations in Mdemodulepkg.dsc vs nt32pkg.dsc. I have
tried every suggestion and made every configuration change possible. Spent
hours google searching the issue. Getting rid of the Null debuglib
reference, using the intel package vs mdepkg and so on. Sorting it out
further unfortunately is beyond my abilities at the moment. I think the
issue is that the debug calls get ignored because a driver based on
Mdemodulepkg is running off of the NT32pkg firmware volume image I copied
from the NT32 build X64 folder into the Mdemodulepkg build x64 folder along
with SecMain so that the VM can run when I type 'Build run -p
mdemodulepkg'. If there is another way to rebuild that firmware volume
someone please clue me in because i think that would fix it. I only know
how to build it from Nt32pkg. In anycase Ill just start over and use the
NT32pkg platform instead.

Thank you

             reply	other threads:[~2017-09-08 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 17:33 david moheban [this message]
2017-09-11  3:03 ` WARNING: No source level debug Gao, Liming
  -- strict thread matches above, loose matches on Subject: below --
2017-09-08  4:02 david moheban
2017-09-08  5:29 ` Gao, Liming

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=CADxnD1yyZuNo9hD0pA8_NEvOV2ngr2acmFDCNV2XrKwO+xPUHg@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