public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26056] SIGSEGV in tui_async_resize_screen -> rl_resize_terminal on SIGWINCH with non-tty stdin/stdout Date: Sun, 09 Aug 2020 18:51:51 +0000 [thread overview] Message-ID: <bug-26056-4717-f2JeQgRRLp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26056-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26056 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2020-08-09 Ever confirmed|0 |1 CC| |tromey at sourceware dot org --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- FWIW this seems to work ok with git gdb. There have been many TUI changes since 8.3, including in the readline initialization area. Could you try git gdb and see if it works? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-09 18:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-27 21:11 [Bug gdb/26056] New: " mpratt at google dot com 2020-08-09 18:51 ` tromey at sourceware dot org [this message] 2020-08-10 14:58 ` [Bug gdb/26056] " mpratt at google dot com 2021-02-10 10:28 ` anudeephomes247 at gmail dot com 2021-02-10 10:30 ` mark at klomp dot org 2021-05-20 12:15 ` tulzakasi at gmail dot com 2021-09-08 8:27 ` ashish.lumar2902 at gmail dot com 2021-12-17 22:12 ` lsix at lancelotsix dot com
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-26056-4717-f2JeQgRRLp@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).