Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: Kevin Buettner <kevinb@redhat.com>,
	gdb-patches@sourceware.org,  Tom de Vries <tdevries@suse.de>,
	Andrew Burgess <aburgess@redhat.com>,
	Pedro Alves <pedro@palves.net>
Subject: Re: [RFC PATCH v2] gdb: Add drgn-why-sleeping command
Date: Sun, 4 Oct 2026 23:23:53 +0200	[thread overview]
Message-ID: <CAJVr-EPA9GibtYjKm2KLJpLYEczhXAkNT=gdfin72tVUoxfdnw@mail.gmail.com> (raw)
In-Reply-To: <87bj9cf09i.fsf@tromey.com>

[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]

On Fri, Oct 2, 2026 at 8:03 PM Tom Tromey <tom@tromey.com> wrote:

> >>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
>
> Kevin> If we had some sort of user-facing contrib directory, it could be
> Kevin> placed there.  Alternately, as the AI reviewer suggested, it could
> Kevin> go into a contrib directory in the drgn package.
>
> FWIW this latter approach makes sense to me.  One idea behind the Python
> extension work is that project-specific things can be shipped with that
> project, and don't need to be in gdb itself.
>
> thanks,
> Tom
>

Hi Tom,

This command is intended for user space debugging while drgn is currently
used
to debug only the kernel. Most user space developers are unaware
that such a tool
even exists. If this script were part of drgn, only a few people would know
about
its existence. If shipped as a part of GDB, it would be exposed to the
regular GDB users
who would actually debug multi-threaded user space programs.

Thank you,
Alexandra

[-- Attachment #2: Type: text/html, Size: 1572 bytes --]

      reply	other threads:[~2026-10-04 21:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 19:00 Alexandra Hájková
2026-10-01  3:40 ` Kevin Buettner
2026-10-01  9:01   ` Alexandra Petlanova Hajkova
2026-10-01 22:50     ` Kevin Buettner
2026-10-02 18:03       ` Tom Tromey
2026-10-04 21:23         ` Alexandra Petlanova Hajkova [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='CAJVr-EPA9GibtYjKm2KLJpLYEczhXAkNT=gdfin72tVUoxfdnw@mail.gmail.com' \
    --to=ahajkova@redhat.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=pedro@palves.net \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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