From: Tom Tromey <tom@tromey.com>
To: Enze Li via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Enze Li <enze.li@hotmail.com>,
enze.li@gmx.com
Subject: Re: [PATCH] gdb/testsuite: update a pattern in gdb_file_cmd
Date: Tue, 13 Dec 2022 09:23:17 -0700 [thread overview]
Message-ID: <87v8mfe0i2.fsf@tromey.com> (raw)
In-Reply-To: <OS3P286MB21527BE6BB9A44FE43E4A0A8F0E39@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (Enze Li via Gdb-patches's message of "Tue, 13 Dec 2022 22:28:27 +0800")
>>>>> "Enze" == Enze Li via Gdb-patches <gdb-patches@sourceware.org> writes:
Enze> I dunno if this file still makes sense, and since it exists, I guess it
Enze> would be appropriate to document it here.
Enze> WDYT?
It's fine by me but I don't think the to-do list is really maintained,
and probably would make more sense to just delete.
Also maybe the remaining self-tests can't be replaced, I'm not sure.
One of them at least is for testing gdb's own pretty-printers, so that
seems pretty difficult.
Really the main problem with these is that they are fragile and, at
least for me, seem to time out a lot (I guess depending on whether I've
done a -g -O0 build or not). So maybe it's better to just try to remove
the flaws.
Tom
prev parent reply other threads:[~2022-12-13 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 13:06 Enze Li
2022-12-07 15:01 ` Simon Marchi
2022-12-08 14:36 ` Tom de Vries
2022-12-09 17:45 ` Tom Tromey
2022-12-13 14:28 ` Enze Li
2022-12-13 16:23 ` Tom Tromey [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=87v8mfe0i2.fsf@tromey.com \
--to=tom@tromey.com \
--cc=enze.li@gmx.com \
--cc=enze.li@hotmail.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).