Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/3] Keep track of files copied to host and target
Date: Fri, 15 Aug 2014 04:04:00 -0000	[thread overview]
Message-ID: <1408075184-25947-1-git-send-email-yao@codesourcery.com> (raw)

In current GDB testsuite, .py files (in gdb.python), file1.txt (in
gdb.dwarf2), and .xml files (in gdb.xml) are copied to host at
the beginning of the tests, and removed at the end of the test.
However, GDB testsuite also copies files to target, but automatically
track them in gdb.exp:cleanfiles, and remove them from target when
each test is finished.

This patch series is teach GDB testsuite to keep track of files copied
to host and remove them when test is finished, the same as what we
did for files copied to target.  The files copied to both target and
host are tracked in an unified way.

Patch #1 is to extend existing cleanfiles for not only target but also
host.  In patch #2, we start to keep track of files copied to host in
cleanfiles, so that each test doesn't have to remove them at the end.
Patch #3 is to copy some needed .py files to host, to fix some fails
in remote host testing.

The patch series is tested in native and gdbserver on x86_64-linux.
I also test it with my local board file to emulate gdb native testing
in a remote host (host == target != build), result looks good.  I'll
tweak it a little and post it shortly.  I also find some tests don't
copy needed file to host, and I'll fix them separately.

*** BLURB HERE ***

Yao Qi (3):
  Extend cleanfiles for multiple hosts
  Keep track of downloaded file in gdb_remote_download
  Copy .py files to remote host

 gdb/testsuite/gdb.base/checkpoint.exp              |  2 --
 gdb/testsuite/gdb.base/step-line.exp               |  2 --
 gdb/testsuite/gdb.dwarf2/dw2-anonymous-func.exp    |  5 +----
 gdb/testsuite/gdb.dwarf2/dw2-basic.exp             |  5 +----
 gdb/testsuite/gdb.dwarf2/dw2-compressed.exp        |  5 +----
 gdb/testsuite/gdb.dwarf2/dw2-filename.exp          |  5 +----
 gdb/testsuite/gdb.dwarf2/dw2-intercu.exp           |  2 --
 gdb/testsuite/gdb.dwarf2/dw2-intermix.exp          |  6 ++----
 gdb/testsuite/gdb.dwarf2/dw2-producer.exp          |  5 +----
 gdb/testsuite/gdb.dwarf2/mac-fileno.exp            |  5 +----
 gdb/testsuite/gdb.python/py-finish-breakpoint.exp  |  6 +++---
 gdb/testsuite/gdb.python/py-finish-breakpoint2.exp |  4 +++-
 gdb/testsuite/gdb.python/py-frame-args.exp         |  2 --
 gdb/testsuite/gdb.python/py-mi.exp                 |  2 --
 gdb/testsuite/gdb.python/py-pp-integral.exp        |  2 --
 gdb/testsuite/gdb.python/py-pp-re-notag.exp        |  2 --
 gdb/testsuite/gdb.python/py-prettyprint.exp        |  4 ----
 gdb/testsuite/gdb.python/py-section-script.exp     |  2 --
 gdb/testsuite/gdb.python/py-typeprint.exp          |  2 --
 gdb/testsuite/gdb.python/py-xmethods.exp           |  2 --
 gdb/testsuite/gdb.python/python.exp                |  7 ++++--
 gdb/testsuite/gdb.stabs/weird.exp                  |  2 --
 gdb/testsuite/gdb.xml/tdesc-regs.exp               |  4 ----
 gdb/testsuite/lib/gdb.exp                          | 25 ++++++++++++++++------
 24 files changed, 37 insertions(+), 71 deletions(-)

-- 
1.9.0


             reply	other threads:[~2014-08-15  4:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15  4:04 Yao Qi [this message]
2014-08-15  4:04 ` [PATCH 1/3] Extend cleanfiles for multiple hosts Yao Qi
2014-08-15  4:04 ` [PATCH 2/3] Keep track of downloaded file in gdb_remote_download Yao Qi
2014-08-15  4:04 ` [PATCH 3/3] Copy .py files to remote host Yao Qi
2014-08-15  5:00 ` [PATCH 0/3] Keep track of files copied to host and target Doug Evans
2014-08-15  6:08   ` Yao Qi
2014-08-16  0:38     ` Doug Evans
2014-08-20  6:54       ` Yao Qi
2014-08-20 15:17         ` Pedro Alves
2014-08-20 15:48         ` Doug Evans
2014-08-21  0:35           ` Yao Qi
2014-08-21 17:32             ` Doug Evans
2014-08-22  6:14               ` Yao Qi

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=1408075184-25947-1-git-send-email-yao@codesourcery.com \
    --to=yao@codesourcery.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