public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCHv3 0/3] Python/TUI Window Creation / Destruction Fixes
Date: Mon, 13 Feb 2023 12:32:44 +0000	[thread overview]
Message-ID: <87lel1u4nn.fsf@redhat.com> (raw)
In-Reply-To: <cover.1674837139.git.aburgess@redhat.com>

Andrew Burgess <aburgess@redhat.com> writes:

> This series conflicted with my other TUI series, that I just merged.
> No real changes in v3, just resolved the merge conflicts.
>
> Changes since v2:
>
>   - Rebased onto HEAD of upsstream, resolved merged conflicts in patch
>     #3.
>
> Changes since v1:
>
>   - Rebased onto HEAD of upstream,
>
>   - Reworded the commit message for patch #2.
>

Ping!  If it helps at all, only patch #2 is really interesting.

Thanks,
Andrew



> ---
>
> Andrew Burgess (3):
>   gdb/python: allow Python TUI windows to be replaced
>   gdb/python: deallocate tui window factories at Python shut down
>   gdb/tui: don't leak the known_window_types map
>
>  gdb/python/py-tui.c                           |  52 ++++++++-
>  gdb/python/python-internal.h                  |   1 +
>  gdb/python/python.c                           |   1 +
>  .../gdb.python/tui-window-factory.exp         | 105 ++++++++++++++++++
>  .../gdb.python/tui-window-factory.py          |  48 ++++++++
>  gdb/tui/tui-layout.c                          |  43 +++----
>  6 files changed, 227 insertions(+), 23 deletions(-)
>  create mode 100644 gdb/testsuite/gdb.python/tui-window-factory.exp
>  create mode 100644 gdb/testsuite/gdb.python/tui-window-factory.py
>
>
> base-commit: 2d46b103a52e4597ee60aa224ef4e5fb225ba893
> -- 
> 2.25.4


  parent reply	other threads:[~2023-02-13 12:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 19:19 [PATCH " Andrew Burgess
2023-01-12 19:19 ` [PATCH 1/3] gdb/python: allow Python TUI windows to be replaced Andrew Burgess
2023-01-12 19:19 ` [PATCH 2/3] gdb/python: deallocate tui window factories at Python shut down Andrew Burgess
2023-01-12 19:19 ` [PATCH 3/3] gdb/tui: don't leak the known_window_types map Andrew Burgess
2023-01-25 13:56 ` [PATCHv2 0/3] Python/TUI Window Creation / Destruction Fixes Andrew Burgess
2023-01-25 13:56   ` [PATCHv2 1/3] gdb/python: allow Python TUI windows to be replaced Andrew Burgess
2023-01-25 13:56   ` [PATCHv2 2/3] gdb/python: deallocate tui window factories at Python shut down Andrew Burgess
2023-01-25 13:56   ` [PATCHv2 3/3] gdb/tui: don't leak the known_window_types map Andrew Burgess
2023-01-27 16:34   ` [PATCHv3 0/3] Python/TUI Window Creation / Destruction Fixes Andrew Burgess
2023-01-27 16:34     ` [PATCHv3 1/3] gdb/python: allow Python TUI windows to be replaced Andrew Burgess
2023-01-27 16:34     ` [PATCHv3 2/3] gdb/python: deallocate tui window factories at Python shut down Andrew Burgess
2023-01-27 16:34     ` [PATCHv3 3/3] gdb/tui: don't leak the known_window_types map Andrew Burgess
2023-02-13 12:32     ` Andrew Burgess [this message]
2023-02-13 14:11       ` [PATCHv3 0/3] Python/TUI Window Creation / Destruction Fixes Tom Tromey
2023-02-13 14:52         ` Andrew Burgess

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=87lel1u4nn.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@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).