From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org, simark@simark.ca, tom@tromey.com
Subject: Re: [PATCH 4/4] gdb: check max-value-size when reading strings for printf
Date: Tue, 04 Jul 2023 16:24:35 +0300 [thread overview]
Message-ID: <83bkgrlsh8.fsf@gnu.org> (raw)
In-Reply-To: <87lefvlsnr.fsf@redhat.com> (message from Andrew Burgess on Tue, 04 Jul 2023 14:20:40 +0100)
> From: Andrew Burgess <aburgess@redhat.com>
> Cc: Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>, Eli
> Zaretskii <eliz@gnu.org>
> Date: Tue, 04 Jul 2023 14:20:40 +0100
>
> Andrew Burgess <aburgess@redhat.com> writes:
>
> Eli,
>
> Did you have any docs feedback?
>
> Thanks,
> Andrew
>
>
> > Tom suggested this change should have a NEWS entry, so I added one.
> > There's no changes to the rest of the patch.
The NEWS entry is OK, thanks.
next prev parent reply other threads:[~2023-07-04 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 9:27 [PATCH 0/4] Some alloca removal and a printf bug fix Andrew Burgess
2023-06-01 9:27 ` [PATCH 1/4] gdb: fix printf of wchar_t early in a gdb session Andrew Burgess
2023-06-02 16:54 ` Tom Tromey
2023-06-01 9:27 ` [PATCH 2/4] gdb: remove two uses of alloca from printcmd.c Andrew Burgess
2023-06-01 9:27 ` [PATCH 3/4] gdb: remove last alloca call " Andrew Burgess
2023-06-01 9:27 ` [PATCH 4/4] gdb: check max-value-size when reading strings for printf Andrew Burgess
2023-06-02 17:05 ` Tom Tromey
2023-06-05 9:43 ` Andrew Burgess
2023-07-04 13:20 ` Andrew Burgess
2023-07-04 13:24 ` Eli Zaretskii [this message]
2023-06-02 17:06 ` [PATCH 0/4] Some alloca removal and a printf bug fix Tom Tromey
2023-07-07 14:34 ` Andrew Burgess
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=83bkgrlsh8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).