From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdb/testsuite] Make tui testing less verbose
Date: Wed, 6 Oct 2021 01:32:09 +0200 [thread overview]
Message-ID: <24207260-f0fb-187d-811f-620aa2d32581@suse.de> (raw)
In-Reply-To: <877derz6fv.fsf@tromey.com>
On 10/5/21 8:12 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Tom> Brings down verbosity to something more reasonable:
> Tom> ...
> Tom> $ wc -l gdb.log
> Tom> 3221 gdb.log
> Tom> ...
>
> Tom> Tested on x86_64-linux.
>
> Tom> Any comments?
>
> It seems fine to me. I don't know what others do, but when I'm
> debugging TUI test cases I normally end up hacking in a bunch of
> dump_screen calls or whatever, as needed, then remove them at the end.
I do the same, and my ambition here was to make adding those calls
superfluous.
> So I'd probably be fine with even less logging.
Ack, but perhaps for maintainers less experienced with TUI test-cases
it'll be easier to parse the initial log and analyze problems (without
requiring them to know where to add those calls).
Thanks,
- Tom
prev parent reply other threads:[~2021-10-05 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 13:22 Tom de Vries
2021-10-05 18:12 ` Tom Tromey
2021-10-05 23:32 ` Tom de Vries [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=24207260-f0fb-187d-811f-620aa2d32581@suse.de \
--to=tdevries@suse.de \
--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).