Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sam James via Gdb <gdb@sourceware.org>
To: Qi Su via Gdb <gdb@sourceware.org>
Cc: Qi Su <qi@fuzz.land>,  jose.marchesi@oracle.com
Subject: Re: [BPF] Maintenance status and breakpoint/register questions
Date: Sun, 03 Aug 2025 11:39:21 +0100	[thread overview]
Message-ID: <87jz3ky9ie.fsf@gentoo.org> (raw)
In-Reply-To: <CAJTrxKCVJ4KJ0Jh_mi59nrV6cUtMxDLD7C0dp5WED2J8sKtkWA@mail.gmail.com>

Qi Su via Gdb <gdb@sourceware.org> writes:

> Hi Jose and gdb folks,
>
> Hope you're doing well. I've been digging into GDB's BPF target and wanted
> to check a few things before I start cleaning up patches.
>
> 1. Maintenance status
> The last commits touching `gdb/bpf` seem over a year old, and I haven’t
> seen much recent activity. Is the port still actively maintained? Also, is
> there any internal code at Oracle—docs, test cases, examples—that could be
> upstreamed or shared?

Ports in gdb don't tend to require particularly high levels of
commits. I'm not saying there isn't stuff to be done, but I don't think
the activity level is alarming (at least to me). 

The only BPF specific file in gdb is gdb/bpf-tdep.c and that's not so
big by design. Is there something more specific you're concerned about?

(I'm not saying there is or isn't some problem with the bpf port, I'm
just curious as I hadn't seen anything as a problem.)

> [...]

sam

  reply	other threads:[~2025-08-03 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-03  7:16 Qi Su via Gdb
2025-08-03 10:39 ` Sam James via Gdb [this message]
2025-08-03 11:51   ` Qi Su via Gdb

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=87jz3ky9ie.fsf@gentoo.org \
    --to=gdb@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=qi@fuzz.land \
    --cc=sam@gentoo.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