public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/26973] gdb crashes when not including the status window in a new layout
Date: Sun, 29 Nov 2020 17:54:48 +0000	[thread overview]
Message-ID: <bug-26973-4717-xCoqd9OwoA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26973-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26973

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-10-branch branch has been updated by Hannes Domani
<ssbssa@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b03dac541f8b2b01c4a562dd4a602f2b5c121aa4

commit b03dac541f8b2b01c4a562dd4a602f2b5c121aa4
Author: Hannes Domani <ssbssa@yahoo.de>
Date:   Thu Nov 19 16:49:53 2020 +0100

    Don't delete the locator win info

    The locator win info is special because it is static, all the others are
    created dynamically.

    gdb/ChangeLog:

    2020-11-29  Hannes Domani  <ssbssa@yahoo.de>

            PR tui/26973
            * tui/tui-layout.c (tui_apply_current_layout): Don't delete the
            static locator win info.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-11-29 17:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 17:40 [Bug tui/26973] New: " ssbssa at sourceware dot org
2020-11-29 17:49 ` [Bug tui/26973] " cvs-commit at gcc dot gnu.org
2020-11-29 17:54 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-29 17:55 ` ssbssa at sourceware dot org
2021-06-27 17:48 ` ahmedsayeed1982 at yahoo dot com
2021-09-02 11:06 ` donipah907 at mtlcz dot com
2021-09-02 11:15 ` mark at klomp dot org
2021-09-05  7:36 ` kimolsun2020 at yahoo dot com
2021-09-06  9:08 ` focixujo at livinginsurance dot co.uk
2021-09-06  9:12 ` focixujo at livinginsurance dot co.uk
2021-09-10 19:36 ` mehmetgelisin at aol dot com
2021-09-14 12:54 ` jarilittlenen at yahoo dot com
2021-09-26 13:31 ` tes.vik1986 at gmail dot com
2021-10-09 11:00 ` gulsenenginar at aol dot com
2021-10-09 16:09 ` studiaviktor at gmail dot com
2021-10-19  7:14 ` progonsaytu at gmail dot com
2021-10-24 10:02 ` glassmtech at ukr dot net
2021-11-13 19:34 ` tesaso8237 at funboxcn dot com
2021-11-22  6:48 ` gexed96894 at keagenan 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-26973-4717-xCoqd9OwoA@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).