Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Qi Su via Gdb <gdb@sourceware.org>
To: Qi Su via Gdb <gdb@sourceware.org>
Cc: jose.marchesi@oracle.com, Sam James <sam@gentoo.org>
Subject: Re: [BPF] Maintenance status and breakpoint/register questions
Date: Sun, 3 Aug 2025 04:51:45 -0700	[thread overview]
Message-ID: <e762c046-8b48-4b10-b3a4-4e6a75291462@fuzz.land> (raw)
In-Reply-To: <87jz3ky9ie.fsf@gentoo.org>


On 8/3/25 03:39, Sam James wrote:
> 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 understand low frequency is fine for ports in gdb. bpf-gdb had very 
little discussion. There's only one bug report #28565 in sourceware 
bugzilla in 2021 and it shows bpf-gdb's simulator was not functional 
(step/run/continue crashes). It's the most basic functionality and had 
not been fixed for a long time and that's why I was asking.

> [...]
Qi

      reply	other threads:[~2025-08-03 11:55 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
2025-08-03 11:51   ` Qi Su via Gdb [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=e762c046-8b48-4b10-b3a4-4e6a75291462@fuzz.land \
    --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