From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Use ui-out tables in linux-tdep.c
Date: Fri, 11 Aug 2023 09:12:24 +0200 [thread overview]
Message-ID: <CAJVr-EPY-JxzCWXgcOhgZhHHpPBge2df5X_-r28OFxAoCcHE9Q@mail.gmail.com> (raw)
In-Reply-To: <20230809-info-proc-ui-out-v1-3-36d4b1b8f582@tromey.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Wed, Aug 9, 2023 at 6:42 PM Tom Tromey <tom@tromey.com> wrote:
> This changes a couple of spots in linux-tdep.c to use a ui-out table.
> It also changes the output to style the file names.
> ---
> gdb/linux-tdep.c | 114
> ++++++++++++++++++++++---------------------------------
> 1 file changed, 46 insertions(+), 68 deletions(-)
>
> Hi,
I regression tested this patch set on aarch64 and there seems to be a
regression - one failure for gdb.base/completion.exp:
(gdb) FAIL: gdb.base/completion.exp: complete 'info registers '
When I run this test on top of the master it passes:
(gdb) PASS: gdb.base/completion.exp: complete 'info registers '
prev parent reply other threads:[~2023-08-11 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 16:40 [PATCH 0/3] Use ui-out tables in a few spots Tom Tromey
2023-08-09 16:40 ` [PATCH 1/3] Use ui-out in maintenance_print_user_registers Tom Tromey
2023-08-11 9:53 ` Christophe Lyon
2023-08-09 16:40 ` [PATCH 2/3] Use ui-out in core_target::info_proc_mappings Tom Tromey
2023-08-09 16:41 ` [PATCH 3/3] Use ui-out tables in linux-tdep.c Tom Tromey
2023-08-11 7:12 ` Alexandra Petlanova Hajkova [this message]
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=CAJVr-EPY-JxzCWXgcOhgZhHHpPBge2df5X_-r28OFxAoCcHE9Q@mail.gmail.com \
--to=ahajkova@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).