From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org, chet.ramey@case.edu
Subject: Re: [PING^3][PATCH][readline] Fix heap-buffer-overflow in update_line
Date: Thu, 11 Jul 2019 20:42:00 -0000 [thread overview]
Message-ID: <87v9w89ucv.fsf@tromey.com> (raw)
In-Reply-To: <40b0c874-9b8e-c6f5-ee3b-401ef0118d9b@suse.de> (Tom de Vries's message of "Thu, 4 Jul 2019 08:09:34 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Apologies for the delay on this.
Tom> Ping^3.
>>>> 2019-05-25 Tom de Vries <tdevries@suse.de>
>>>> Chet Ramey <chet.ramey@case.edu>
>>>>
>>>> PR cli/24514
>>>> * readline/display.c (init_line_structures, rl_redisplay): Ensure
>>>> line_size is at least _rl_screenwidth + 1.
I don't know this part of readline very well. However, if Chet approved
it and/or put it into upstream readline, then it is fine for gdb.
thanks,
Tom
next prev parent reply other threads:[~2019-07-11 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 11:25 [PATCH][readline] " Tom de Vries
2019-06-10 18:36 ` [PING][PATCH][readline] " Tom de Vries
2019-06-17 9:38 ` [PING^2][PATCH][readline] " Tom de Vries
2019-07-04 6:09 ` [PING^3][PATCH][readline] " Tom de Vries
2019-07-11 20:42 ` Tom Tromey [this message]
2019-07-12 13:35 ` Chet Ramey
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=87v9w89ucv.fsf@tromey.com \
--to=tom@tromey.com \
--cc=chet.ramey@case.edu \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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