public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: krishnaLee <sssky307@163.com>
To: edk2-devel@lists.01.org
Subject: How to do source level debug (OVMF & QEMU & Intel UEFI Development Debugger Tool)
Date: Thu, 26 Apr 2018 11:12:04 +0800 (CST)	[thread overview]
Message-ID: <34737459.4fe1.162ffefbc32.Coremail.sssky307@163.com> (raw)

Hi everyone,
I know nothing about this source level debug mode so I had read some articles and  tried to make this environment,but failed.
I do this as I want to observe how SEC phase jump to PEI phase. 


#1 build ovmf:
build -p OvmfPkg/OvmfPkgIa32.dsc -a IA32 -D DEBUG_ON_SERIAL_PORT -D SOURCE_DEBUG_ENABLE
#2 run it alone,ok
qemu-system-x86_64.exe -machine pc-q35-2.9 -pflash OVMF32-source-debug.fd -serial stdio 
#3 redirect serial to tcp,it hints "info: QEMU waiting for connection on: disconnected:tcp:::1:1234,server"
qemu-system-x86_64.exe -machine pc-q35-2.9 -pflash OVMF32_source_debug.fd -serial tcp:localhost:1234,server
#4,execute "C:\Program Files (x86)\Intel\Intel(R) UEFI Development Kit Debugger Tool\eXdi.exe" /LaunchWinDbg" with follow settings,but failed connect to qemu.
# error message box"Unable to open TCP address(localhost:1234):No connection could be made because the target machine actively refused it"
[Debug Port]
Channel = TCP
Server = localhost
Port = 1234


I also tried using pipe and com port, all can't connect to qemu,it is very appreciate if anyone could give any baby steps...


# other information:
my windows:win10 x64
QEMU version:2.10
UDK2017
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86(install by default settings)
Intel UEFI Development Debugger Tool 1.5(install by default settings)




thank you
by krishna

                 reply	other threads:[~2018-04-26  3:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=34737459.4fe1.162ffefbc32.Coremail.sssky307@163.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