All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: linux-debuggers@vger.kernel.org
Subject: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, May 24th
Date: Tue, 23 May 2023 13:48:01 -0700	[thread overview]
Message-ID: <877csy7p1a.fsf@oracle.com> (raw)

Hello everyone!

After two months off, the next Linux Kernel Debugging Tools monthly
meeting is tomorrow: Wednesday, May 24th at 11:30am Pacific time.
The agenda is a bit light so far: please feel free to reply to this
message with suggested topics.

The virtual meeting link is changed from the calendar invite, since Omar
is still on leave. Please email me off-list if you'd like to join. If
you're on the calendar invite, you should have received a separate email
from me containing the link.

* Linux Plumber's Conference is November 13th-15th, and there is a
  proposed microconference for Linux Kernel Debugging Tools [1]. There
  is a lot of exciting work going on in our area, so please do submit to
  speak there.

* [ Your topic here? ]

* If there's no other topics, I can give a brief update / shameless plug
  of the current DWARFless debugging [2] branch of Drgn. True to its
  name, it allows you to run Drgn without DWARF debuginfo (instead using
  kallsyms and CTF).

As you can see, not too much on the agenda, but I always find that these
meetings stir up interesting discussion that wasn't planned, so I'd
encourage you to show up anyway. Worst case, we chat for a bit and leave
early for lunch!

Thanks,
Stephen

[1]: https://lpc.events/event/17/page/200-proposed-microconferences#debugging
[2]: https://github.com/osandov/drgn/issues/176

             reply	other threads:[~2023-05-23 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 20:48 Stephen Brennan [this message]
2023-05-24 19:48 ` Linux Kernel Debugging Tools Monthly Meeting on Wednesday, May 24th 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=877csy7p1a.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.