From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Handle unreachable network in server-connect.exp
Date: Wed, 18 Sep 2019 21:27:00 -0000 [thread overview]
Message-ID: <871rwdthw0.fsf@tromey.com> (raw)
In-Reply-To: <5f724500-d168-9bbb-139f-c455899b6c82@suse.de> (Tom de Vries's message of "Wed, 18 Sep 2019 13:55:56 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> So, I'm attaching an updated patch that does not modify the existing
Tom> semantics of gdb_target_cmd.
Tom> 2019-09-14 Tom de Vries <tdevries@suse.de>
Tom> * lib/gdbserver-support.exp (gdb_target_cmd_ext): Return 2 (meaning
Tom> UNSUPPORTED) for 'Network is unreachable' message. Factor out of ...
Tom> (gdb_target_cmd): ... here.
Tom> * gdb.server/server-connect.exp: Use gdb_target_cmd_ext, handle return
Tom> value 2.
Thanks you for doing this. This is ok.
Tom
next prev parent reply other threads:[~2019-09-18 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 10:23 Tom de Vries
2019-09-17 15:40 ` Sergio Durigan Junior
2019-09-17 18:01 ` Tom Tromey
2019-09-18 11:56 ` Tom de Vries
2019-09-18 21:27 ` Tom Tromey [this message]
2019-09-18 23:16 ` Tom de Vries
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=871rwdthw0.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).