public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Stepan via groups.io" <radio-fan=mail.ru@groups.io>
To: "Guo Dong" <guo.dong@intel.com>, devel@edk2.groups.io
Subject: [edk2-devel] UefiPayloadPkg debugging
Date: Sun, 23 Mar 2025 23:05:24 -0700	[thread overview]
Message-ID: <15989.1742796324617653799@groups.io> (raw)
In-Reply-To: <CY5PR11MB6260ED0EEA2542DC14425C3A9EDE2@CY5PR11MB6260.namprd11.prod.outlook.com>

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

Hello,

Hmm, that's weird. Source debugging is working for universal payload, which builded by python UefiPayloadPkg/UniversalPayloadBuild.py -a IA32 -b DEBUG -t GCC5 -D SOURCE_DEBUG_ENABLE=TRUE. But payload, which builded by python UefiPayloadPkg/UniversalPayloadBuild.py -a IA32 -b DEBUG -t GCC5 -D SOURCE_DEBUG_ENABLE=TRUE is not starting.
It works similarly for non-universal load:

build -a X64 -p UefiPayloadPkg/UefiPayloadPkg.dsc -b DEBUG -t GCC5 : is not starting
build -a IA32 -a X64 -p UefiPayloadPkg/UefiPayloadPkg.dsc -b DEBUG -t GCC5 : is working with debugging


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121216): https://edk2.groups.io/g/devel/message/121216
Mute This Topic: https://groups.io/mt/111746873/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



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

      reply	other threads:[~2025-03-24  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 11:01 [edk2-devel] UefiPayloadPkg debugging Stepan via groups.io
2025-03-18  4:20 ` Stepan via groups.io
2025-03-18  5:00   ` Chiu, Chasel via groups.io
2025-03-18  5:19     ` Guo Dong via groups.io
2025-03-24  6:05       ` Stepan via groups.io [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=15989.1742796324617653799@groups.io \
    --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