Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Some TUI fixes
Date: Tue, 08 Nov 2016 18:57:00 -0000	[thread overview]
Message-ID: <1478631454-9447-1-git-send-email-arnez@linux.vnet.ibm.com> (raw)

This is a small series for fixing some problems in the TUI logic.  The
first patch fixes a GDB crash, while the other patches make some of the
surrounding logic more consistent and readable.

Andreas Arnez (4):
  tui-disasm: Fix window content buffer overrun
  tui-disasm: Fix line buffer size calculation
  tui-winsource: Allocate for actual lines only
  tui-winsource: Remove failed-allocation logic

 gdb/testsuite/gdb.base/tui-layout.c   | 30 ++++++++++++++++++++++++
 gdb/testsuite/gdb.base/tui-layout.exp | 17 +++++++++++---
 gdb/tui/tui-disasm.c                  | 43 ++++++++++++++++-------------------
 gdb/tui/tui-winsource.c               | 22 ++++--------------
 4 files changed, 69 insertions(+), 43 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/tui-layout.c

-- 
2.5.0


             reply	other threads:[~2016-11-08 18:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 18:57 Andreas Arnez [this message]
2016-11-08 18:58 ` [PATCH 1/4] tui-disasm: Fix window content buffer overrun Andreas Arnez
2016-11-08 19:29   ` Pedro Alves
2016-11-09 12:07     ` Andreas Arnez
2016-11-08 18:59 ` [PATCH 2/4] tui-disasm: Fix line buffer size calculation Andreas Arnez
2016-11-08 19:30   ` Pedro Alves
2016-11-08 18:59 ` [PATCH 3/4] tui-winsource: Allocate for actual lines only Andreas Arnez
2016-11-08 19:31   ` Pedro Alves
2016-11-08 19:00 ` [PATCH 4/4] tui-winsource: Remove failed-allocation logic Andreas Arnez
2016-11-08 19:31   ` Pedro Alves

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=1478631454-9447-1-git-send-email-arnez@linux.vnet.ibm.com \
    --to=arnez@linux.vnet.ibm.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