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 v2 4/4] [gdb/testsuite] Move gdb.base/gdb-caching-proc.exp to gdb.testsuite
Date: Mon, 6 Mar 2023 16:45:48 +0100 [thread overview]
Message-ID: <7c8370b8-f550-d61a-73dd-772e744425d0@suse.de> (raw)
In-Reply-To: <87h6uy6in0.fsf@tromey.com>
On 3/6/23 15:48, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Tom> Test-case gdb.base/gdb-caching-proc.exp doesn't really test gdb, but it tests
> Tom> the gdb_caching_procs in the testsuite, so it belongs in gdb.testsuite rather
> Tom> than gdb.base.
>
> Tom> Move test-case gdb.base/gdb-caching-proc.exp to gdb.testsuite, renaming it to
> Tom> gdb.testsuite/gdb-caching-proc-consistency.exp to not clash with
> Tom> recently added gdb.testsuite/gdb-caching-proc.exp.
>
> Tom> Tested on x86_64-linux.
>
> I agree, seems fine, though I don't understand why it wasn't just
> created there?
The test-case gdb.base/gdb-caching-proc.exp was by added by this commit:
...
commit 64d27cfc97f5b865019f0b7293ff2b9565db427c
Author: Tom de Vries <tdevries@suse.de>
Date: Sat Dec 1 08:56:56 2018 +0100
...
The dir gdb.testsuite was added by this commit:
...
commit 213fd9faf563ce5726ce66c8104cbaba44ba9c09
Author: Pedro Alves <palves@redhat.com>
Date: Thu Jul 4 16:45:23 2019 +0100
...
In other words, the test-case wasn't created in gdb.testsuite because it
predates gdb.testsuite.
Thanks for the reviews, I'll commit shortly.
Thanks,
- Tom
> Reviewed-By: Tom Tromey <tom@tromey.com>
>
> Tom
next prev parent reply other threads:[~2023-03-06 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 9:35 [PATCH v2 1/4] [gdb/testsuite] Add gdb.testsuite/gdb-caching-proc.exp Tom de Vries
2023-03-04 9:35 ` [PATCH v2 2/4] [gdb/testsuite] Use regular proc syntax for gdb_caching_proc Tom de Vries
2023-03-06 14:20 ` Tom Tromey
2023-03-04 9:35 ` [PATCH v2 3/4] [gdb/testsuite] Allow args in gdb_caching_proc Tom de Vries
2023-03-06 14:23 ` Tom Tromey
2023-03-04 9:35 ` [PATCH v2 4/4] [gdb/testsuite] Move gdb.base/gdb-caching-proc.exp to gdb.testsuite Tom de Vries
2023-03-06 14:48 ` Tom Tromey
2023-03-06 15:45 ` Tom de Vries [this message]
2023-03-06 14:47 ` [PATCH v2 1/4] [gdb/testsuite] Add gdb.testsuite/gdb-caching-proc.exp 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=7c8370b8-f550-d61a-73dd-772e744425d0@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).