From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: LABARTHE Guillaume <guillaume.labarthe@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: [RFC][PATCH] new-ui command under windows using NamedPipe
Date: Fri, 19 Jul 2019 08:54:00 -0000 [thread overview]
Message-ID: <a3234fe8-1082-b2f6-1d21-3a7f240e3d8e@redhat.com> (raw)
In-Reply-To: <20190719085035.GX23204@embecosm.com>
On 7/19/19 9:50 AM, Andrew Burgess wrote:
>> I tried it on GNU/Linux and things still work.
>>
>> I ran all the MI tests with forced new-ui, with:
>>
>> $ make check TESTS="gdb.mi/*.exp" RUNTESTFLAGS="FORCE_MI_SEPARATE_UI=1"
>>
>> and saw no regressions.
>
> Are all of these special flags for testing documented anywhere? Every
> now and then someone will mention some new flag that I've never seen
> before and I always think that one day it might be helpful...
Yes, in gdb/testsuite/README:
~~~~
FORCE_SEPARATE_MI_TTY
Setting FORCE_MI_SEPARATE_UI to 1 forces all MI testing to start GDB
in console mode, with MI running on a separate TTY, on a secondary UI
started with "new-ui".
~~~~
Thanks,
Pedro Alves
prev parent reply other threads:[~2019-07-19 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 18:41 LABARTHE Guillaume
2019-07-18 16:24 ` Pedro Alves
2019-07-19 8:50 ` Andrew Burgess
2019-07-19 8:54 ` Pedro Alves [this message]
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=a3234fe8-1082-b2f6-1d21-3a7f240e3d8e@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=guillaume.labarthe@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