From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/9] [gdb/testsuite] Fix remote target test fails
Date: Tue, 15 Nov 2022 15:30:16 +0100 [thread overview]
Message-ID: <f45ba051-c016-1f31-66a4-6b12b67de124@suse.de> (raw)
In-Reply-To: <20221107161333.16999-1-tdevries@suse.de>
On 11/7/22 17:13, Tom de Vries via Gdb-patches wrote:
> Fix testsuite failures with target board remote-gdbserver-on-localhost.
>
> This is a follow-up on the proposed patch series
> https://sourceware.org/pipermail/gdb-patches/2022-October/193147.html by
> Ivan Tetyushkin. I started from scratch, but borrowed from the original
> series, so I've marked that by using co-authored-by.
>
> This patch series takes a different approach than the original proposal:
> rather than trying to construct absolute file names that will work on the
> remote target, make things work with the names as returned by remote_download.
>
> One of the fixes is to add a REMOTE_TARGET_USERNAME parameter to the target
> board, such that we can limit file permissions to get a more realistic
> emulation of an actual remote target, and this allows us to reproduce the
> failures reported by Ivan.
>
> Tested on x86_64-linux, using target board remote-gdbserver-on-localhost.
>
Pushed.
Thanks,
- Tom
> Tom de Vries (9):
> [gdb/testsuite] Fix gdb.base/foll-exec.exp for remote target
> [gdb/testsuite] Fix gdb.base/info_sources_2.exp for remote target
> [gdb/testsuite] Add REMOTE_TARGET_USERNAME in
> remote-gdbserver-on-localhost.exp
> [gdb/testsuite] Fix gdb.base/print-file-var.exp for remote target
> [gdb/testsuite] Fix gdb.base/infcall-exec.exp for remote target
> [gdb/testsuite] Fix gdb.base/solib-vanish.exp for remote target
> [gdb/testsuite] Fix gdb.base/info-shared.exp for remote target
> [gdb/testsuite] Fix gdb.base/jit-reader-exec.exp for remote target
> [gdb/testsuite] Fix gdb.base/jit-elf-so.exp for remote target
>
> .../boards/remote-gdbserver-on-localhost.exp | 30 +++++++++++-
> .../gdb.base/exec-invalid-sysroot.exp | 4 ++
> gdb/testsuite/gdb.base/foll-exec.exp | 4 ++
> gdb/testsuite/gdb.base/foll-vfork.exp | 4 ++
> gdb/testsuite/gdb.base/infcall-exec.c | 48 ++++++++++++++++++-
> gdb/testsuite/gdb.base/infcall-exec.exp | 10 +++-
> gdb/testsuite/gdb.base/info-shared.exp | 11 ++++-
> gdb/testsuite/gdb.base/info_sources_2.exp | 12 +++++
> gdb/testsuite/gdb.base/jit-elf-so.exp | 11 +++--
> gdb/testsuite/gdb.base/jit-reader-exec.exp | 14 ++++--
> gdb/testsuite/gdb.base/print-file-var.exp | 6 ++-
> gdb/testsuite/gdb.base/solib-vanish.exp | 17 +++++--
> gdb/testsuite/lib/gdb.exp | 40 ++++++++++------
> 13 files changed, 174 insertions(+), 37 deletions(-)
>
>
> base-commit: 8bfb6941c358ee2da8320125644c59bf90842f6b
prev parent reply other threads:[~2022-11-15 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 16:13 Tom de Vries
2022-11-07 16:13 ` [PATCH 1/9] [gdb/testsuite] Fix gdb.base/foll-exec.exp for remote target Tom de Vries
2022-11-07 16:13 ` [PATCH 2/9] [gdb/testsuite] Fix gdb.base/info_sources_2.exp " Tom de Vries
2022-11-07 16:13 ` [PATCH 3/9] [gdb/testsuite] Add REMOTE_TARGET_USERNAME in remote-gdbserver-on-localhost.exp Tom de Vries
2022-11-08 9:18 ` Tom de Vries
2022-11-09 20:49 ` Tom de Vries
2022-11-15 14:31 ` Tom de Vries
2022-11-07 16:13 ` [PATCH 4/9] [gdb/testsuite] Fix gdb.base/print-file-var.exp for remote target Tom de Vries
2022-11-07 16:13 ` [PATCH 5/9] [gdb/testsuite] Fix gdb.base/infcall-exec.exp " Tom de Vries
2022-11-07 16:13 ` [PATCH 6/9] [gdb/testsuite] Fix gdb.base/solib-vanish.exp " Tom de Vries
2022-11-07 16:13 ` [PATCH 7/9] [gdb/testsuite] Fix gdb.base/info-shared.exp " Tom de Vries
2022-11-07 16:13 ` [PATCH 8/9] [gdb/testsuite] Fix gdb.base/jit-reader-exec.exp " Tom de Vries
2022-11-07 16:13 ` [PATCH 9/9] [gdb/testsuite] Fix gdb.base/jit-elf-so.exp " Tom de Vries
2022-11-15 14:30 ` 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=f45ba051-c016-1f31-66a4-6b12b67de124@suse.de \
--to=tdevries@suse.de \
--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).