From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Fix testing gdb.rust/modules.exp against gdbserver
Date: Thu, 16 Nov 2017 17:51:00 -0000 [thread overview]
Message-ID: <87k1yq8637.fsf@tromey.com> (raw)
In-Reply-To: <1510852993-26330-1-git-send-email-palves@redhat.com> (Pedro Alves's message of "Thu, 16 Nov 2017 17:23:13 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> gdb/ChangeLog:
Pedro> 2017-11-16 Pedro Alves <palves@redhat.com>
Pedro> * gdb.rust/modules.exp: Skip tests that rely on inferior I/O if
Pedro> gdb,noinferiorio is set, and use gdb_test_stdio otherwise.
Thanks, this looks reasonable to me.
Tom
next prev parent reply other threads:[~2017-11-16 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 17:23 Pedro Alves
2017-11-16 17:51 ` Tom Tromey [this message]
2017-11-16 18:09 ` Pedro Alves
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=87k1yq8637.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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