From: Serapheim Dimitropoulos <serapheimd@gmail.com>
To: osandov@osandov.com
Cc: linux-debuggers@vger.kernel.org
Subject: Re: Debugging Microconference at Linux Plumbers Conference?
Date: Thu, 9 Apr 2026 10:41:44 -0400 [thread overview]
Message-ID: <20260409144144.72399-1-sdimitropoulos@coreweave.com> (raw)
In-Reply-To: <adaxdvQvJX318oy9@telecaster>
On Wed, Apr 08, 2026 at 12:50:14PM -0700, Omar Sandoval wrote:
> We are gauging interest in hosting another Debugging Microconference at
> Linux Plumbers Conference this year. Topics would focus on common
> challenges people are facing with debugging tooling: collecting and
> analyzing core dumps, doing live analysis, developing more powerful
> debugger features and tools, etc.
I'd be interested in attending and potentially starting a discussion
over a few things that we've been working on at CoreWeave!
Specifically:
(1) Capturing crash dumps with tight memory and space constraints at
scale
(2) Triaging, deduplicating, and categorizing crash dumps in
production
(3) We've been experimenting with out-of-band kernel introspection
(using drgn in a DPU to introspect the host with one-sided RDMA
ops). Would be cool to see if others have worked on the same or
similar problems.
Thanks,
Serapheim
prev parent reply other threads:[~2026-04-09 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 19:50 Debugging Microconference at Linux Plumbers Conference? Omar Sandoval
2026-04-09 14:41 ` Serapheim Dimitropoulos [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=20260409144144.72399-1-sdimitropoulos@coreweave.com \
--to=serapheimd@gmail.com \
--cc=linux-debuggers@vger.kernel.org \
--cc=osandov@osandov.com \
/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