From: Tom de Vries <tdevries@suse.de>
To: Pedro Alves <palves@redhat.com>,
Philippe Waroquiers <philippe.waroquiers@skynet.be>,
gdb-patches@sourceware.org
Subject: [PATCH OB][gdb/testsuite] Move valgrind-db-attach.{c,exp} to valgrind-bt.{c,exp}
Date: Thu, 25 Oct 2018 14:26:00 -0000 [thread overview]
Message-ID: <aba47719-aa39-ccc4-daad-f839a30f6194@suse.de> (raw)
In-Reply-To: <00acc1fb-6b79-82ff-80d3-fb770e58f77a@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
[ was: Re: [OB PATCH][gdb/testsuite] Handle removed valgrind option
--db-attach ]
On 10/25/18 2:16 PM, Pedro Alves wrote:
>> (perhaps with a rename to valgrind-bt.{exp,c})?
> Yeah, that sounds good. But I'd do it as follow up, to help
> archaeology, by helping git's renaming detection algorithm.
Done. Committed as attached.
Thanks,
- Tom
[-- Attachment #2: 0001-gdb-testsuite-Move-valgrind-db-attach.-c-exp-to-valgrind-bt.-c-exp.patch --]
[-- Type: text/x-patch, Size: 1072 bytes --]
[gdb/testsuite] Move valgrind-db-attach.{c,exp} to valgrind-bt.{c,exp}
Now that valgrind-db-attach.exp no longer use --db-attach, rename
valgrind-db-attach.{c,exp} to valgrind-bt.{c,exp}.
2018-10-05 Tom de Vries <tdevries@suse.de>
* gdb.base/valgrind-db-attach.c: Rename to ...
* gdb.base/valgrind-bt.c: ... this.
* gdb.base/valgrind-db-attach.exp: Rename to ...
* gdb.base/valgrind-bt.exp: ... this.
---
gdb/testsuite/gdb.base/{valgrind-db-attach.c => valgrind-bt.c} | 0
gdb/testsuite/gdb.base/{valgrind-db-attach.exp => valgrind-bt.exp} | 0
2 files changed, 0 insertions(+), 0 deletions(-)
diff --git a/gdb/testsuite/gdb.base/valgrind-db-attach.c b/gdb/testsuite/gdb.base/valgrind-bt.c
similarity index 100%
rename from gdb/testsuite/gdb.base/valgrind-db-attach.c
rename to gdb/testsuite/gdb.base/valgrind-bt.c
diff --git a/gdb/testsuite/gdb.base/valgrind-db-attach.exp b/gdb/testsuite/gdb.base/valgrind-bt.exp
similarity index 100%
rename from gdb/testsuite/gdb.base/valgrind-db-attach.exp
rename to gdb/testsuite/gdb.base/valgrind-bt.exp
next prev parent reply other threads:[~2018-10-25 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181024111355.GA13788@delia>
2018-10-24 16:29 ` [OB PATCH][gdb/testsuite] Handle removed valgrind option --db-attach Pedro Alves
2018-10-24 19:34 ` Tom de Vries
2018-10-24 20:50 ` Philippe Waroquiers
2018-10-25 10:09 ` Tom de Vries
2018-10-25 12:16 ` Pedro Alves
2018-10-25 14:26 ` Tom de Vries [this message]
2018-10-25 15:08 ` [PATCH][gdb/testsuite] Factor out lib/valgrind.exp Tom de Vries
2018-10-25 15:25 ` Pedro Alves
2018-10-25 20:03 ` Philippe Waroquiers
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=aba47719-aa39-ccc4-daad-f839a30f6194@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=philippe.waroquiers@skynet.be \
/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