diff options
author | Oliver Smith-Denny <osde@microsoft.com> | 2025-07-21 14:57:04 -0700 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2025-07-23 12:57:55 +0000 |
commit | bcd8509640aa067d01fccc5fbdc021c149b64ebe (patch) | |
tree | d4709ed7130661076fc2f9caa6b64ed735d80d9e /BaseTools/Source/Python | |
parent | 1ec1f5d711b47a9f9aca86b4089f21af4c8a17ac (diff) | |
download | edk2-bcd8509640aa067d01fccc5fbdc021c149b64ebe.zip edk2-bcd8509640aa067d01fccc5fbdc021c149b64ebe.tar.gz edk2-bcd8509640aa067d01fccc5fbdc021c149b64ebe.tar.bz2 |
StandaloneMmPkg: Always Print Driver Load Messages
Today, StandaloneMM Core's image loader only prints driver load messages
if debug code is enabled. However, these are some of the most
important prints in the codebase: on a given system even if you
have nothing else to debug with, you can see the last driver
executed.
Debug code blocks are used to skip logic that only exists for
debug purposes and wastes time on a release build. However, the
logic to print a line and determine the filename from the PDB
is not extensive and provides critical information, so it is
inappropriate to wrap in a debug code section.
Platforms can still choose to disable logging at DEBUG_INFO/DEBUG_LOAD
and will not see the error messages.
Signed-off-by: Oliver Smith-Denny <osde@microsoft.com>
Diffstat (limited to 'BaseTools/Source/Python')
0 files changed, 0 insertions, 0 deletions