From: Dmitry Antipov <dantipov@nvidia.com>
To: GDB Development <gdb@sourceware.org>
Subject: Testing with remote gdbserver
Date: Thu, 08 Feb 2018 14:29:00 -0000 [thread overview]
Message-ID: <1eca7308-60e6-5c39-1eae-1f9dc1c034f1@nvidia.com> (raw)
Hello,
are there any known-to-work board configuration files to test gdbserver remotely?
After reading https://sourceware.org/gdb/wiki/TestingGDB, I supposed that this
has to be relatively simple, at least between two GNU/Linux x86 machines with public
key-based ssh access between them. But, since I just have a) noise about missing 'runtest'
(which is /usr/bin/runtest in my $PATH), b) a lot of FAILED messages (probably due to
communication timeouts) and c) time-to-time zombie ssh processes, I assume that my setup
is grossly misconfigured at some non-obvious but very important point. I've started
from example remote board file taken from "Testing gdbserver in a remote cross-target
configuration" of the above and tried some tweaks, but still have no PASSes (except
for local libiberty tests). Is it possible to run the tests in a "much more verbose"
mode to check what's going on?
Thanks in advance,
Dmitry
next reply other threads:[~2018-02-08 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 14:29 Dmitry Antipov [this message]
2018-02-08 15:50 ` Yao Qi
2018-02-08 16:28 ` Simon Marchi
2018-02-08 16:31 ` Simon Marchi
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=1eca7308-60e6-5c39-1eae-1f9dc1c034f1@nvidia.com \
--to=dantipov@nvidia.com \
--cc=gdb@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