public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/30056] double free when using reverse-search for a previous command and Ctrl-C
Date: Sun, 28 May 2023 08:27:20 +0000 [thread overview]
Message-ID: <bug-30056-4717-gN88Tqgkep@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30056-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30056
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
Target Milestone|--- |14.1
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed by commit in the in-repo copy of readline.
The problem is still there for system readlines that miss this patch, but
AFAICT there's nothing we can do about this in gdb.
That is, maybe we could fix half of the problem by not returning '\0' to
readline, but instead call tui_getc_1 in a loop until it returns something not
'\0'. But the other half of the problem would still exist and cause the same
problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-05-28 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:47 [Bug tui/30056] New: " etesta at undo dot io
2023-01-27 3:04 ` [Bug tui/30056] " sam at gentoo dot org
2023-01-28 20:00 ` ssbssa at sourceware dot org
2023-05-23 8:38 ` vries at gcc dot gnu.org
2023-05-23 9:53 ` vries at gcc dot gnu.org
2023-05-23 10:29 ` vries at gcc dot gnu.org
2023-05-23 11:50 ` vries at gcc dot gnu.org
2023-05-23 15:06 ` vries at gcc dot gnu.org
2023-05-23 16:06 ` vries at gcc dot gnu.org
2023-05-24 14:11 ` vries at gcc dot gnu.org
2023-05-28 8:17 ` cvs-commit at gcc dot gnu.org
2023-05-28 8:27 ` vries at gcc dot gnu.org [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=bug-30056-4717-gN88Tqgkep@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).