public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: devel@edk2.groups.io, cheptsov@ispras.ru
Cc: "Gao, Liming" <liming.gao@intel.com>,
	"Marvin Häuser" <mhaeuser@outlook.de>
Subject: Re: [edk2-devel] CLANGPDB binary debugging
Date: Fri, 20 Mar 2020 12:14:15 -0700	[thread overview]
Message-ID: <7E18AD8F-9A44-45FE-A8C8-CE06A6328930@apple.com> (raw)
In-Reply-To: <9804C565-0C9E-4778-92A7-06EA6AD8D694@ispras.ru>

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



> On Mar 20, 2020, at 8:13 AM, Vitaly Cheptsov <cheptsov@ispras.ru> wrote:
> 
> Hello,
> 
> We noticed that the original bugzilla, which intended to add new LLVM toolchain support[1], also wanted to bring ELF format support with DWARF debugging information. For some reason this did not make its way into EDK II, and we are currently wondering, how can one debug binaries built with LLVM 9.0.
> 
> For macOS and XCODE5 toolchain we use GDB scripts based on Andrei Warkentin’s work, which allow us to integrate with QEMU and VMware[2]. It is likely that they should work with little to no work on Linux with CLANG38/GCC5 with GDB once again. However, CLANGPDB apparently is using PDB debugging information, which I believe is not handled with GDB.
> 
> Could you please provide the details on the matter and let us know about the recommended route?
> — Is dropping CLANGELF just a temporary measure and it should be resubmitted again?
> — Should LLDB, which seems to be aware of PDB, be used instead of GDB, when building with CLANGPDB? If so, did anybody try that?
> 

Vitaly,

I've not tried the CLANGPDB path, but if you want to connect lldb to QEMU you need to set  plugin.process.gdb-remote.target-definition-file [1] to [2]. 

[1]  lldb -o "settings set plugin.process.gdb-remote.target-definition-file x86_64_target_definition.py" -o "gdb-remote 9000"
[2] https://github.com/llvm-mirror/lldb/blob/master/examples/python/x86_64_target_definition.py

Thanks,

Andrew Fish

> Thanks!
> 
> Best regards,
> Vitaly
> 
> [1] https://bugzilla.tianocore.org/show_bug.cgi?id=1603 <https://bugzilla.tianocore.org/show_bug.cgi?id=1603>
> [2] https://github.com/acidanthera/OpenCorePkg/blob/master/Debug/Scripts/gdb_uefi.py <https://github.com/acidanthera/OpenCorePkg/blob/master/Debug/Scripts/gdb_uefi.py>
> 
> 


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

  reply	other threads:[~2020-03-20 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 15:13 CLANGPDB binary debugging Vitaly Cheptsov
2020-03-20 19:14 ` Andrew Fish [this message]
2020-03-21 10:28   ` [edk2-devel] " Vitaly Cheptsov
2020-03-21 17:13     ` Andrew Fish
2020-03-21 18:36       ` Vitaly Cheptsov
2020-03-21 21:06         ` Andrew Fish
2020-03-23  9:10           ` Vitaly Cheptsov
2020-03-25 13:16             ` Liming Gao
2020-03-25 13:20               ` Vitaly Cheptsov

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=7E18AD8F-9A44-45FE-A8C8-CE06A6328930@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