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 gdb/26768] New: [gdb] Import readline copy Date: Wed, 21 Oct 2020 23:47:08 +0000 [thread overview] Message-ID: <bug-26768-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26768 Bug ID: 26768 Summary: [gdb] Import readline copy Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Our current readline version is 8.0 patchlevel 4. Readline-8.1-rc1 has been out since two weeks, and an 8.1 release is expected. I've been told that preliminary testing of gdb against a libreadline build from Readline-8.1-rc1 shows that the problem for which this: ... 2019-07-12 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. ... was committed not longer occurs, so presumably that commit can be dropped when doing the import, and perhaps also the followup commit: ... 2019-10-23 Andrew Burgess <andrew.burgess@embecosm.com> PR cli/24980 * display.c (init_line_structures): Initialise line_state using original minsize value. ... FWIW, to reproduce the heap-buffer-overflow: ... $ ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD=/usr/lib64/libasan.so.6 TERM="dumb" gdb -ex "set width 0" ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-10-21 23:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-21 23:47 vries at gcc dot gnu.org [this message] 2021-08-15 19:39 ` [Bug gdb/26768] " tromey at sourceware dot org 2024-01-05 13:52 ` ssbssa at sourceware dot org 2024-01-10 18:39 ` tromey at sourceware dot org
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-26768-4717@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: linkBe 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).