Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2] gcore: Handle unreadable pages within readable memory regions
Date: Tue, 17 Feb 2026 21:22:57 +0000	[thread overview]
Message-ID: <SN7PR11MB76382C6D1329221436E328DEF96DA@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20260217111658.0671d87f@f42-zbm-amd>

> -----Original Message-----
> From: Kevin Buettner <kevinb@redhat.com>
> Sent: Dienstag, 17. Februar 2026 19:17
> To: Schimpe, Christina <christina.schimpe@intel.com>
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH v2] gcore: Handle unreadable pages within readable
> memory regions
> 
> On Tue, 17 Feb 2026 17:44:06 +0000
> "Schimpe, Christina" <christina.schimpe@intel.com> wrote:
> 
> > > Claude Opus 4.5 and GLM 4.7 assisted with the development of this
> > > commit.
> >
> > For binutils there is a guideline for LLM generated content:
> > https://sourceware.org/binutils/wiki/LLM_Generated_Content
> >
> > Do we have something similar for GDB ?
> 
> Not yet.  IMO, the GDB project should adopt the same guidelines that binutils
> uses.  Until we have a policy in place, I encourage all GDB contributors to
> follow the binutils policy when using LLMs.

Thank you for the clarification.

> For my contributions to the GDB project, I am using AI / LLMs to help me
> understand code and diagnose problems, but I am instructing the models I
> use to not generate patches for me, nor show me new code.
> Instead, I am instructing them to write English language descriptions of how
> the code might be fixed as part of its analysis.  With that in hand, I write the
> patch myself.
> 
> E.g.  I used Claude Code yesterday to find a problem in what I thought to be a
> bit of build infrastructure.  (But it turned out to be a bug in GDB's testsuite,
> for which I'll be submitting a patch.)  In any case, once it had found the bug, I
> instructed it:
> 
>   Please make a markdown file describing the problem in detail along
>   with your fix proposals.  Place the markdown file in the home
>   directory ($HOME) and tell me the path to it when you're done.  I
>   will likely go with option 2 in which I submit a patch fixing this
>   problem, but I may wish to discuss it with my colleagues first,
>   which is why I want a comprehensive write-up.  Don't show your fixes
>   in the form of patches; instead describe in English how the bug
>   might be fixed for each of your proposals.  The reason for this is
>   that, although GDB does not have an AI/LLM policy yet, many other
>   related projects (such as binutils and elfutils) are instituting
>   policies about LLM generated code.  So...  I don't want a patch from
>   you, merely really good documentation about what the problem is and
>   English language descriptions about how it may be fixed.  You may,
>   of course, show existing code and its problems in your summary.  You
>   just can't show me new code which fixes the problem.
> 
> Instructions like this might also be placed in a CLAUDE.md or AGENTS.md file.

And thanks a lot for your detailed response here.

Christina
Intel Deutschland GmbH
Registered Address: Dornacher Straße 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht München HRB 186928

      reply	other threads:[~2026-02-17 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 19:39 Kevin Buettner
2026-02-17 14:19 ` Tom de Vries
2026-02-17 17:50   ` Kevin Buettner
2026-02-17 17:44 ` Schimpe, Christina
2026-02-17 18:16   ` Kevin Buettner
2026-02-17 21:22     ` Schimpe, Christina [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=SN7PR11MB76382C6D1329221436E328DEF96DA@SN7PR11MB7638.namprd11.prod.outlook.com \
    --to=christina.schimpe@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.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