From: Chet Ramey <chet.ramey@case.edu>
To: Tom de Vries <tdevries@suse.de>,
gdb-patches@sourceware.org, bug-readline@gnu.org
Cc: chet.ramey@case.edu
Subject: Re: [PATCH] [readline] Fix double free in _rl_scxt_dispose
Date: Sat, 27 May 2023 15:10:55 -0400 [thread overview]
Message-ID: <d3e1cef2-d8d6-2ec9-7369-1176f8f3b7c3@case.edu> (raw)
In-Reply-To: <20230523160431.28769-1-tdevries@suse.de>
On 5/23/23 12:04 PM, Tom de Vries wrote:
> Both these issues need fixing independently, though after fixing the first we
> no longer trigger the second.
Thanks for the report. These are both good fixes.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2023-05-27 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 16:04 Tom de Vries
2023-05-24 18:13 ` Andrew Burgess
2023-05-24 18:31 ` Tom de Vries
2023-05-24 18:39 ` Chet Ramey
2023-05-27 19:10 ` Chet Ramey [this message]
2023-05-28 8:20 ` Tom de Vries
2023-05-29 16:43 ` Simon Marchi
2023-05-29 16:50 ` Tom de Vries
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=d3e1cef2-d8d6-2ec9-7369-1176f8f3b7c3@case.edu \
--to=chet.ramey@case.edu \
--cc=bug-readline@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).