From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Move gdbserver to top level
Date: Sun, 09 Feb 2020 14:17:00 -0000 [thread overview]
Message-ID: <4d5a1276-91aa-7197-5f90-854767987f73@suse.de> (raw)
In-Reply-To: <0b6b4f24-f5c8-b236-c249-737e70395667@suse.de>
On 09-02-2020 14:59, Tom de Vries wrote:
> On 03-02-2020 22:34, Tom Tromey wrote:
>> I'm going to push it tomorrow or the day after, unless there's some
>> objection.
>
> Hi,
>
> FYI, starting this commit, I'm running into:
> ...
> (gdb) PASS: gdb.multi/multi-target.exp: continue: non-stop=off: set
> remote-exec file in inferior 2
> spawn of --once --multi localhost:2346 failed
> ERROR: tcl error sourcing
> /data/gdb_versions/devel/src/gdb/testsuite/gdb.multi/multi-target.exp.
> ERROR: Timeout waiting for gdbserver response.
Looking at other tests that use gdbserver, I guess this is missing:
...
diff --git a/gdb/testsuite/gdb.multi/multi-target.exp
b/gdb/testsuite/gdb.multi/multi-target.exp
index 3588eb4d76..6c727b5e3b 100644
--- a/gdb/testsuite/gdb.multi/multi-target.exp
+++ b/gdb/testsuite/gdb.multi/multi-target.exp
@@ -17,6 +17,10 @@
load_lib gdbserver-support.exp
+if { [skip_gdbserver_tests] } {
+ return 0
+}
+
standard_testfile
# The plain remote target can't do multiple inferiors.
...
[ It would be nice though if the gdbserver tests will work again, given
that I'm actually building gdbserver. ]
Thanks,
- Tom
next prev parent reply other threads:[~2020-02-09 14:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 20:07 Tom Tromey
2020-01-21 5:34 ` Simon Marchi
2020-01-23 22:03 ` Tom Tromey
2020-01-24 14:29 ` Hannes Domani via gdb-patches
2020-01-24 15:12 ` Tom Tromey
2020-01-24 15:57 ` Tom Tromey
2020-01-24 16:02 ` Hannes Domani via gdb-patches
2020-01-24 16:28 ` Tom Tromey
2020-01-24 16:35 ` Hannes Domani via gdb-patches
2020-01-24 19:03 ` Hannes Domani via gdb-patches
2020-01-24 15:23 ` Pedro Alves
2020-01-25 0:07 ` Tom Tromey
2020-01-25 16:55 ` Pedro Alves
2020-01-26 16:01 ` Tom Tromey
2020-01-27 18:13 ` Pedro Alves
2020-01-28 0:37 ` Tom Tromey
2020-02-03 21:34 ` Tom Tromey
2020-02-07 16:06 ` Simon Marchi
2020-02-09 13:59 ` Tom de Vries
2020-02-09 14:17 ` Tom de Vries [this message]
2020-02-10 10:01 ` Tom de Vries
2020-02-10 15:54 ` Sergio Durigan Junior
2020-02-12 0:55 ` Tom Tromey
2020-02-12 16:47 ` Sergio Durigan Junior
2020-02-14 3:54 ` Sergio Durigan Junior
2020-02-14 18:43 ` Tom Tromey
2020-02-14 21:14 ` Tom Tromey
2020-02-17 13:58 ` Luis Machado
2020-02-17 14:21 ` Maciej W. Rozycki
2020-02-17 14:29 ` Luis Machado
2020-02-17 16:57 ` Luis Machado
2020-02-17 17:01 ` Tom Tromey
2020-02-17 17:28 ` Aktemur, Tankut Baris
2020-02-17 18:46 ` Tom Tromey
2020-02-10 10:59 ` [PATCH][gdb/testsuite] Skip multi-target.exp without gdbserver Tom de Vries
2020-02-10 12:20 ` Pedro Alves
2020-02-09 23:05 ` [PATCH] Move gdbserver to top level Alan Modra
2020-02-10 12:02 ` Pedro Alves
2020-02-10 9:52 ` Andreas Schwab
2020-02-10 12:13 ` Pedro Alves
2020-02-10 13:04 ` Andreas Schwab
2020-02-10 13:15 ` Andreas Schwab
2020-02-11 13:48 ` [PATCH] Disable gdbserver on host != target configurations (Re: [PATCH] Move gdbserver to top level) Pedro Alves
2020-02-11 15:29 ` 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=4d5a1276-91aa-7197-5f90-854767987f73@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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