From: Omar Sandoval <osandov@osandov.com>
To: linux-debuggers@vger.kernel.org
Subject: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, January 28th
Date: Mon, 26 Jan 2026 15:49:27 -0800 [thread overview]
Message-ID: <aXf9h7kERxEANIQf@telecaster> (raw)
The next Linux Kernel Debugging Tools meeting is this Wednesday, January
28th at 11:30 AM Pacific time. This meeting is a forum to discuss
development of Linux kernel debugging tools like drgn, crash, and more.
Here is the agenda so far:
- drgn crash compatibility status update: what's left?
https://github.com/osandov/drgn/issues/507
- Memory searching in drgn status update.
- Dealing with remote/non-ELF kernel debugging in drgn
(https://github.com/osandov/drgn/pull/587,
https://github.com/osandov/drgn/issues/591).
- Dealing with address translation loops in drgn
(https://github.com/osandov/drgn/issues/592,
https://github.com/osandov/drgn/issues/566).
Also a heads up: I will be out of the office from February 23-March 27.
Please reply with anything else you'd like to add. As always, if you
would like to attend, please email me offlist.
Thanks!
Omar
reply other threads:[~2026-01-26 23:49 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-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=aXf9h7kERxEANIQf@telecaster \
--to=osandov@osandov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox