Re: [PATCH v2] gcore: Handle unreadable pages within readable memory regions

[Kevin Buettner <kevinb@redhat.com>]

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.

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.

Kevin