public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: Rebecca Cran <rebecca@nuviainc.com>
Cc: devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH 0/3] Add support for gdb and lldb
Date: Wed, 11 Aug 2021 16:22:39 -0700	[thread overview]
Message-ID: <3710C965-2995-44D4-AF85-CA554C25915A@apple.com> (raw)
In-Reply-To: <776e36f8-df13-8b9d-7c22-948f64af65d7@nuviainc.com>



> On Aug 11, 2021, at 3:11 PM, Rebecca Cran <rebecca@nuviainc.com> wrote:
> 
> I realized the Arm gcc 10.3 aarch64 download from https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads uses Python 2.7.18 and not Python 3, so the f-Strings and likely more cause problems. I suspect at this point there's little point putting effort into supporting Python 2.
> 

I’ve not tested on ARM yet, so please let me know if it works. I’d like to avoid Python 2.7 support is possible given it is passed its best by date. 

> 
> I noticed a couple of issues though: in efi_debugging.py the Attributes text is partially underlined with the non-ASCII characters '——————' instead of '----------'.
> 

Thanks did not notice that. 

>      Attributes
>      ——————----
>      _dict_ : dictionay
> 
> 
> There are also a couple of typos of 'dictionary':
> 
> 
> _dict_ : dictionay
> 

Shoot though I fixed those 

Thanks,

Andrew Fish

> 
> -- 
> Rebecca Cran
> 
> 
> On 8/8/21 3:46 PM, Andrew Fish via groups.io wrote:
>> This patch set adds debugging support for gdb and lldb.
>> It also adds generic debugging classes that use a file like object to
>> make it easy to import into any debugger that supports Python.
>> 
>> Since these debugging scripts don't depend on any EFI code I was thinking
>> we could place them in the root of the repo to be easy to discover.
>> 
>> I've tested gdb on Ubuntu and lldb on macOS for IA32 and X64.
>> 
>> Andrew Fish (3):
>>   efi_debugging.py: - Add debugger agnostic debugging Python Classes
>>   efi_gdb.py: - Add gdb EFI commands and pretty Print
>>   efi_lldb.py: - Add lldb EFI commands and pretty Print
>> 
>>  efi_debugging.py | 2187 ++++++++++++++++++++++++++++++++++++++++++++++
>>  efi_gdb.py       |  918 +++++++++++++++++++
>>  efi_lldb.py      | 1044 ++++++++++++++++++++++
>>  3 files changed, 4149 insertions(+)
>>  create mode 100755 efi_debugging.py
>>  create mode 100755 efi_gdb.py
>>  create mode 100755 efi_lldb.py
>> 


  reply	other threads:[~2021-08-11 23:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-08 21:46 [PATCH 0/3] Add support for gdb and lldb Andrew Fish
2021-08-08 21:46 ` [PATCH 1/3] efi_debugging.py: - Add debugger agnostic debugging Python Classes Andrew Fish
2021-08-08 21:46 ` [PATCH 2/3] efi_gdb.py: - Add gdb EFI commands and pretty Print Andrew Fish
2021-08-08 21:46 ` [PATCH 3/3] efi_lldb.py: - Add lldb " Andrew Fish
2021-08-11 22:11 ` [edk2-devel] [PATCH 0/3] Add support for gdb and lldb Rebecca Cran
2021-08-11 23:22   ` Andrew Fish [this message]
2021-08-12  0:30     ` Rebecca Cran
2021-08-12 22:56       ` Andrew Fish
2021-08-13  5:09         ` Rebecca Cran
2021-09-14 23:47 ` Rebecca Cran
2021-09-15  0:47   ` Andrew Fish
2021-10-23  2:07     ` Rebecca Cran
2021-12-13 21:59     ` Rebecca Cran
     [not found]     ` <16C06F6B056C6852.12686@groups.io>
2022-01-07  2:42       ` Rebecca Cran

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=3710C965-2995-44D4-AF85-CA554C25915A@apple.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