From: Tom Kacvinsky via Gdb <gdb@sourceware.org>
To: GDB <gdb@sourceware.org>
Subject: Re: Problems building GC 18.1 on CentOS 7
Date: Mon, 5 Oct 2026 07:58:26 -0400 [thread overview]
Message-ID: <CAG_eJLe_qexUjHx4w6cQG2sX2KN7nde9VnmRbrtcLD7qpdRr6Q@mail.gmail.com> (raw)
In-Reply-To: <50fdb6e1-7f2e-45d8-bdee-fe740dba9d32@redhat.com>
Hi Guinevere,
On Mon, Oct 5, 2026 at 7:28 AM Guinevere Larsen <guinevere@redhat.com> wrote:
>
>
> On 10/3/26 4:18 PM, Tom Kacvinsky via Gdb wrote:
> > I used Claude Opus 5 to generate a patch and manually inspected it.
> > I am not sure what the GDB policy is for AI assisted patches.
> As I understand it, we're not allowing any AI code in the project, as we
> don't know to whom the copyright belongs, and thus can't be sure that it
> can be transferred to the FSF
>
I think that is completely fair. If you go look at the bug I filed,
Simon cannot
reproduce the problem, and I think that is because I am behind on the CentOS
version I am using. So I think the best bet is just to close the bug
with "won't
fix" and then I'll just carry on with my patches internal to my employer. We do
not ship gdb - so we are not in violation of the GPL license. I am just building
the latest, greatest for use by developers.
Thanks,
Tom
prev parent reply other threads:[~2026-10-05 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 19:18 Tom Kacvinsky via Gdb
2026-10-03 20:47 ` Tom Kacvinsky via Gdb
2026-10-03 22:05 ` Simon Marchi via Gdb
2026-10-03 22:25 ` Tom Kacvinsky via Gdb
2026-10-04 1:55 ` Tom Kacvinsky via Gdb
2026-10-05 11:28 ` Guinevere Larsen via Gdb
2026-10-05 11:58 ` Tom Kacvinsky 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=CAG_eJLe_qexUjHx4w6cQG2sX2KN7nde9VnmRbrtcLD7qpdRr6Q@mail.gmail.com \
--to=gdb@sourceware.org \
--cc=tkacvins@gmail.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