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, June 28th
Date: Wed, 28 Jun 2023 13:19:36 -0700	[thread overview]
Message-ID: <ZJyV2LxQklawQXK9@telecaster> (raw)
In-Reply-To: <ZJtA+PV/ZMxOCnqp@telecaster>

On Tue, Jun 27, 2023 at 01:05:12PM -0700, Omar Sandoval wrote:
> Hello! The next Linux Kernel Debugging Tools meeting is tomorrow,
> Wednesday, June 28nd at 11:30 AM Pacific time. This meeting is a forum
> to discuss development of Linux kernel debugging tools like drgn, crash,
> and more. I'm back from my parental leave, so I'll be hosting again
> (thanks, Stephen, for hosting while I was out).
> 
> The agenda so far is:
> 
> - The Linux Kernel Debugging microconference was accepted for Linux Plumbers.
>   Please submit talk proposals! We can discuss what people are planning
>   to present.
> - ORC format changes (see https://github.com/osandov/drgn/issues/303).
> - Upcoming drgn release.
> 
> Feel free to reply with anything else you'd like to add to the agenda.
> If you would like to attend, please email me offlist.
> 
> Thanks!
> Omar

Here are notes from the meeting:

- Guilherme G. Piccoli from Igalia joined and discussed some of the work he's doing to enable debugging on the Steam Deck. He's mainly using pstore with the ramoops backend.
- Stephen discussed the topic he's planning for the debugging microconference at LPC: an update on debugging without DWARF (using kallsyms and BTF/CTF instead).
- Guilherme discussed his microconference topic around general pstore awareness and improvements.
- We agreed that it makes sense for the microconference to not be strictly limited to "debuggers", but rather debugging as a whole.
- Omar hasn't decided what he's going to present. Perhaps something about fixing the pain points in debugging kernel code across versions/configurations (by using enums instead of macros, making it easy to bootstrap the debugger by providing enough information about memory layout, etc.).
- Stephen also mentioned his idea for providing BPF programs in the kernel that export knowledge of data structures to debuggers, which by his admission would be a ton of work but could help with a lot of portability issues.
- Omar gave an update on handling the ORC format change in drgn. This is now done.
- Omar is planning a new release of drgn this week.

See everyone next month!

      reply	other threads:[~2023-06-28 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 20:05 Linux Kernel Debugging Tools Monthly Meeting on Wednesday, June 28th Omar Sandoval
2023-06-28 20:19 ` 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=ZJyV2LxQklawQXK9@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