From: Andreas Schwab <schwab@suse.de>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix gdb.base/attach.exp fails when gdb is configured --with-sysroot=/
Date: Wed, 24 Jan 2018 16:03:00 -0000 [thread overview]
Message-ID: <mvmzi53qm5i.fsf@suse.de> (raw)
In-Reply-To: <1516809167-10599-1-git-send-email-yao.qi@linaro.org> (Yao Qi's message of "Wed, 24 Jan 2018 15:52:47 +0000")
On Jan 24 2018, Yao Qi <qiyaoltc@gmail.com> wrote:
> 2018-01-24 Yao Qi <yao.qi@linaro.org>
>
> * gdb.base/attach.exp (do_attach_tests): Set sysroot to ".*".
.* can match newlines, better avoid that.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-01-24 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 15:52 Yao Qi
2018-01-24 16:03 ` Andreas Schwab [this message]
2018-01-24 16:12 ` Yao Qi
2018-02-01 14:51 ` Yao Qi
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=mvmzi53qm5i.fsf@suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).