Linux debuggers
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-debuggers@vger.kernel.org
Subject: Re: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, March 27th
Date: Wed, 27 Mar 2024 13:10:11 -0700	[thread overview]
Message-ID: <ZgR9IxhRywJKYX3H@telecaster> (raw)
In-Reply-To: <ZgNQ3Q0UGRJ0oNP5@telecaster>

On Tue, Mar 26, 2024 at 03:49:01PM -0700, Omar Sandoval wrote:
> The next Linux Kernel Debugging Tools meeting is tomorrow, Wednesday,
> March 27th at 11:30 AM Pacific time. This meeting is a forum to discuss
> development of Linux kernel debugging tools like drgn, crash, and more.

Meeting notes:

- We discussed whether we wanted to do another Linux kernel debugging
  microconference at Linux Plumbers Conference this year. The consensus
  was no, at least for this year -- instead, we'll do some BoFs to share
  debugging demos and tips. If we do decide we want some microconference
  discussions, we can submit them to the tracing microconference.
- Neal Gompa brought up the lack of educational content about debugging.
  This is a problem we're all acutely aware of, but many of us who are
  knowledgable enough to create such content tend to be busy developing
  the tools instead. Help is needed here.
- We discussed sframes, and particularly how to avoid distros and
  tooling stripping them, which tied into education.
- I shared that the drgn module API is nearing completion. The two
  biggest missing pieces are documentation and ELF symbol support.
  Stephen Brennan shared that he already had code for kallsyms that
  could be adapted for ELF symbols.
- Stephen Brennan discussed his latest drgn PR for DWARFless debugging:
  https://github.com/osandov/drgn/pull/388.
- We discussed replacing our Slack workspace with an open source
  alternative. With some helpful input from Neal Gompa and Jay Kamat, we
  decided that Matrix would be a good fit. Given the low traffic of our
  workspace, we will start with a single Matrix room for everyone
  (developers and users), and we can split it up as needed. I'll share
  an update on the linux-debuggers mailing list when it's set up.

See everyone next month!

      reply	other threads:[~2024-03-27 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 22:49 Linux Kernel Debugging Tools Monthly Meeting on Wednesday, March 27th Omar Sandoval
2024-03-27 20:10 ` Omar Sandoval [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-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=ZgR9IxhRywJKYX3H@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