From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [PATCH 0/2] Changes to cli-out.c for field alignment and formatting
Date: Tue, 20 Nov 2018 20:30:00 -0000 [thread overview]
Message-ID: <cover.1542745482.git.andrew.burgess@embecosm.com> (raw)
A couple of changes in cli-out that change how fields are formatted.
--
Andrew Burgess (2):
gdb: Respect field width and alignment for 'fmt' fields in CLI output
gdb: Use string_printf to format int fields instead of a fixed size
buffer
gdb/ChangeLog | 13 ++++++++++++
gdb/breakpoint.c | 3 ---
gdb/cli-out.c | 14 ++++++-------
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.opt/inline-break.exp | 36 ++++++++++++++++++++++++++++++++++
5 files changed, 60 insertions(+), 11 deletions(-)
--
2.14.5
next reply other threads:[~2018-11-20 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 20:30 Andrew Burgess [this message]
2018-11-20 20:30 ` [PATCH 1/2] gdb: Respect field width and alignment for 'fmt' fields in CLI output Andrew Burgess
2018-11-20 22:17 ` Tom Tromey
2018-11-20 20:30 ` [PATCH 2/2] gdb: Use string_printf to format int fields instead of a fixed size buffer Andrew Burgess
2018-11-20 22:18 ` Tom Tromey
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=cover.1542745482.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.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