public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Lee Fisher" <lee@preossec.com>
To: devel@edk2.groups.io, guomin.jiang@intel.com,
	"df7729@gmail.com" <df7729@gmail.com>
Subject: Re: [edk2-devel] Using debugger to debug UEFI application?
Date: Tue, 26 May 2020 17:25:00 -0700	[thread overview]
Message-ID: <afc5437d-2913-844e-fd1e-86182df7cf0d@preossec.com> (raw)
In-Reply-To: <DM6PR11MB295524A3961853B6C8C1B76A9DB10@DM6PR11MB2955.namprd11.prod.outlook.com>

> [...]I just found the Intel UDK debugger and hopping to use it [...]

I may be wrong, but I think Intel has put the Intel UDK debugger
solution as End-Of-Life. I'm not sure it's worth spending any time using
an end-of-life'd debugger solution. I think the main 2 alternatives to
the Intel UDK solution are: Intel System Studio (ISS), or Tianocore's
SourceLevelDebugPkg.

Over time, ISS has only been available if you registered, or not even as
freeware, so was only an option for some. But currently ISS is
freely-available without registration. ISS is not end-of-life, and I
presume they have a tech support team to help paying users with
questions, if that helps with your current situation.

There is at least one gdb-server project for UEFI outside the Intel UDK
solution and outside Tianocore:

https://github.com/night199uk/edk2-gdb-server

I think there is a second one, but I can't find it at the moment. I wish
Intel would open-source the Intel UDK debugger code, including it's
gdb-server, instead of just killing it off. Perhaps the Tiancore
community would make use of some of the code. Anything to improve UEFI
debugging is a worthy effort. 

Servers aside, I really I wish there there was an lldb.efi and a gdb.efi...


      reply	other threads:[~2020-05-27  0:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  7:31 Using debugger to debug UEFI application? David F.
2020-05-27  0:00 ` [edk2-devel] " Guomin Jiang
2020-05-27  0:25   ` Lee Fisher [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=afc5437d-2913-844e-fd1e-86182df7cf0d@preossec.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