From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id LVGFMAsNj2gl4gIAWB0awg (envelope-from ) for ; Sun, 03 Aug 2025 03:17:31 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=rwN7hoEq; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id B26591E102; Sun, 3 Aug 2025 03:17:31 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-9.1 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_VALIDITY_CERTIFIED,RCVD_IN_VALIDITY_RPBL, RCVD_IN_VALIDITY_SAFE autolearn=ham autolearn_force=no version=4.0.1 Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 3E2531E089 for ; Sun, 3 Aug 2025 03:17:29 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id A58013858CB6 for ; Sun, 3 Aug 2025 07:17:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A58013858CB6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1754205448; bh=clVAb+YFjzxxXFqBAQ6DM5oDHRhumq8LzzAcRZHD45E=; h=Date:Subject:To:Cc:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=rwN7hoEqOgNzvCwjZpDPDim0YMnUZu6IW36bOqvNXeFdpd5/QGbSaKrSeCJRnjaMz pmJhGwz2OOub797+richbqTZ74XIcBjDHFfKpCU+8p+nB0+eUqdVio3TD2v/Lha398 Iebkxl3RPXybmCjh7qBrlhjJJHub+FMEWXg6Pwys= Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) by sourceware.org (Postfix) with ESMTPS id 8A8B43858C83 for ; Sun, 3 Aug 2025 07:16:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8A8B43858C83 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8A8B43858C83 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754205403; cv=none; b=WrOkdyCefiGhWOs39QcklEZEe9rze+u5q7VFmkLvFef6QbY//GD440UJLNIGJ7pt89e/phCGXDnVcmi6Nv5tHCtftJal7//wQfkzNs76J4WIu4e7tOZMTq7zoupAijMBzI5FiZ8IbDkj+W8aAwNLT6JxR0GyUuA2ilje/mioYGQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754205403; c=relaxed/simple; bh=HiH7HU0ah01KfqGNx0ny02LaABJs2PLs+7BSVwnI69s=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=u0VRQcP4O/nzrpeS364UzJ2Y98eG3a0yDBzZtA/f7iyuU5BK09kF89OOi6JlxKiq0m6pN3o5DlJkYqxRX98Mr+91//nmCOsonL4Gbqj69VALBDsey6H3sJt25XmuSf6VyYC0ABNrb34qF7h2rVC/oK3esNtCToofFwgX49NHThE= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8A8B43858C83 Received: by mail-qt1-x836.google.com with SMTP id d75a77b69052e-4aeb2f73fc0so31225981cf.2 for ; Sun, 03 Aug 2025 00:16:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754205402; x=1754810202; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=HiH7HU0ah01KfqGNx0ny02LaABJs2PLs+7BSVwnI69s=; b=gey1k1KUmV/jgQ1gFnAcjy3/7f1ocs1w+H0IeVJEwG1Yla1KUdc8/qbuxwVTnvATiE u2uxQ+VBm5ZjYnwtI/7gZLvhh+zdh+wmo72UDNpx62qiYFODFmUBSTi+mEWUNGReOWWV l3I2+X7W76GiiVhJVds+zl/JVozQ9DQSfpi/p8NjolZc5sRHgq/YaDFUfk4mcSBijI8v R1GiyYYCjlz/Tuq3nLAVb0NBkNbO+GjPtK+qL8IB+vL0HP2n6Z0g7IDsVyghjKN9dN/x 1crf1EYem/1Ro4FkI/tQM05TMz01zok/tHnyPeyT7EqRtKKtCzhAtdaQzMtIxz8TPWIJ K5tg== X-Gm-Message-State: AOJu0Yyv1gP4l0CwUzja3iSmq/92dbtUm5jZs2wuMTqhDnIgVo6uLt5Z GoisgM8io274AIOUu1axnSj3uLtCaW/LcHYVt33gDFyWG4uPeMcXSKCsIX6UnoR1zB2rwbgaWOm gDxbxzFHKpxrqM6o9xBdRC72uxFbhFYZK/+RrDRErhU15LU0G++GZos4bZA== X-Gm-Gg: ASbGncvvtzZepVQBrJnTqJCznU8TCFL1/E609kAzQ6nQzxxIici0VB2h8KjhIMFr/rz RQaq4B7f4vy4+S84E0eoAdQRJhJ0aN6D/0zd82ysIBpJtAofQs+AeCVt0X6MR2jWa3PwXgUDUEp wyIoiEpd606jGT6fGN7RY/Zchq0UneTtPp3etb3Hf0boaSw6rYeTY/qkfNC+Z0IUxu9OUj+14MY tHT9uItUli8viLJrw== X-Google-Smtp-Source: AGHT+IECtZjeiIR6YIfriEhBXtdTDe64zTKnX1EbMmmaRTqNzTPDyGfnHS1O8wiYVcmSiJ7+L95/WAkstu1jEvO8xGY= X-Received: by 2002:ac8:5a03:0:b0:4ab:9586:bdd9 with SMTP id d75a77b69052e-4af10d03b34mr78993111cf.56.1754205401908; Sun, 03 Aug 2025 00:16:41 -0700 (PDT) MIME-Version: 1.0 Date: Sun, 3 Aug 2025 00:16:31 -0700 X-Gm-Features: Ac12FXzRX0gZMN_Hn5Fl9F9GioQ16AhX57fsUv-mIVBGjSzOw5r_Xv0HBPSlCYQ Message-ID: Subject: [BPF] Maintenance status and breakpoint/register questions To: gdb@sourceware.org Cc: jose.marchesi@oracle.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.30 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Qi Su via Gdb Reply-To: Qi Su Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" 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=E2=80= =99t seen much recent activity. Is the port still actively maintained? Also, is there any internal code at Oracle=E2=80=94docs, test cases, examples=E2=80= =94that could be upstreamed or shared? 2. Breakpoint decode issue (BPF_INSN_BRKPT) BPF_INSN_BRKPT is used for breakpoint injection, but the version requirement is BPF_XBPF, which isn=E2=80=99t valid in normal object files. = That causes gdb to fail decoding breakpoints. Would removing the version check for BPF_INSN_BRKPT be acceptable, or are there side effects to be aware of? 3. gdbstub register description (r10, pc) bpf_register_type() assigns builtin_data_ptr and builtin_func_ptr to r10 and pc without forcing width. That leads to gdb assuming 32-bit sizes, breaking remote stub communication. Two possible fixes: + Explicitly use builtin_int64 for both; + Enable xml register description for bpf so the stub can specify widths directly. Do you have a preference? I lean toward xml=E2=80=94it seems more future-pr= oof=E2=80=94but wasn=E2=80=99t sure if avoiding xml was intentional. Let me know your thoughts. I=E2=80=99m happy to send patches depending on t= he direction that makes sense. Best, Qi