From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: linux-debuggers@vger.kernel.org
Subject: Re: LPC BoF - Linux Kernel Debugging & Drgn
Date: Thu, 19 Sep 2024 08:14:25 -0700 [thread overview]
Message-ID: <87msk33cby.fsf@oracle.com> (raw)
In-Reply-To: <87ploz3hh5.fsf@oracle.com>
Hi everyone,
Thank you for joining the BoF, by all indication it was quite
successful, despite my apparent attempts at sabotage by changing the
room last minute. I took notes as we went (though couldn't cover
everything), which I've included below.
Thanks,
Stephen
---
* Drgn within IPython notebooks! Useful to help people follow & understand debugging sessions. -Shung-Hsi Yu
* What is the criteria for "contrib/" vs "helpers/"? - Sweet Tea Dorminy.
-> Unit test cases!
-> Converting contrib/ to helpers/ is a valid and good on-ramp to drgn development.
-> Though, not all contrib scripts are expected to make it in.
-> There is also a "tools/" directory which is actually tested & supported.
* Is there a "rosetta stone" comparison between operations in drgn and crash?
-> Not currently!
-> I (Stephen) have some which I could move out of an internal wiki into Drgn's wiki.
* Drgn "commands" vs Crash commands. Drgn does not yet have a command structure, it's been discussed.
* What is the status of drgn without debuginfo? https://github.com/osandov/drgn/issues/176
-> Symbol tables implemented, kallsyms in review.
-> Minimal BTF implementation, has some issues.
-> CTF is used in production at Oracle.
* What is the "backend" of drgn? How could you glue kgdb into Drgn?
-> The memory reader interface is the main way.
-> In addition to implementing memory readers, you'd need a way to communicate the "vmcoreinfo" to drgn. This provides info such as kernel version and kaslr offset.
-> We have a way to provide vmcoreinfo manually.
-> we're discussing gdbstub options: https://github.com/osandov/drgn/wiki/gdbstub-protocol-proposal:-linux.vmcoreinfo-query-packet
* What's the minimum I need to do with root in drgn?
-> just opening /proc/kcore
* Writing to kernel memory! New feature as of yesterday!
-> See https://blog.osandov.com/2024/09/17/calling-linux-kernel-functions-from-userspace.html
Please join our Kernel Debuggers Matrix:
https://matrix.to/#/#linux-debuggers:matrix.org
Please join our Kernel Debuggers Mailing List:
linux-debuggers@vger.kernel.org
next prev parent reply other threads:[~2024-09-19 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 23:26 LPC BoF - Linux Kernel Debugging & Drgn Stephen Brennan
2024-09-19 13:23 ` Stephen Brennan
2024-09-19 15:14 ` Stephen Brennan [this message]
2024-09-19 15:24 ` Stephen Brennan
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-all 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=87msk33cby.fsf@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=linux-debuggers@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.