public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marvin Häuser" <Marvin.Haeuser@outlook.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: david moheban <moheban79@gmail.com>
Subject: Re: Curious question regarding lack of debug in MdeModulePkg
Date: Fri, 8 Sep 2017 03:12:39 +0000	[thread overview]
Message-ID: <AM4PR06MB149131EDBCEEAFBD7B19A1D480950@AM4PR06MB1491.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <CADxnD1xawfDme1pG3KDozeb45E=TFNFRMSRUNQuCRWXg5BEHTg@mail.gmail.com>

Hey,

Did you make sure you use the proper DebugLib instance in your .dsc (or if you build MdeModulePkg directly, adapted its)? You likely want UefiDebugLibConOut.
Also make sure you enabled the necessary debug levels via PCD.

Regards,
Marvin.

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> david moheban
> Sent: Friday, September 8, 2017 4:53 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Curious question regarding lack of debug in MdeModulePkg
> 
> Hi,
> 
> Was trying to figure out why I could not output debug messages with a
> simple driver using the Debug macro compiled against the MdeModulePkg
> until I discovered that the same driver code works when compiled against
> Nt32Pkg and all my debug messages get posted in the debug console. Would
> anyone happen to know why?
> 
> Thank you
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08  2:52 Curious question regarding lack of debug in MdeModulePkg david moheban
2017-09-08  3:12 ` Marvin Häuser [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=AM4PR06MB149131EDBCEEAFBD7B19A1D480950@AM4PR06MB1491.eurprd06.prod.outlook.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