From: Doug Evans <dje@google.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] New option --cygwin-tty.
Date: Fri, 26 Jul 2013 19:40:00 -0000 [thread overview]
Message-ID: <CADPb22QfOzhV7r6QGVZ8y2DHTdTXA6MzaG3=CHZGq0A-rgz+ag@mail.gmail.com> (raw)
In-Reply-To: <51F0D9D2.1090804@codesourcery.com>
On Thu, Jul 25, 2013 at 12:54 AM, Yao Qi <yao@codesourcery.com> wrote:
> On 07/25/2013 03:37 PM, Pierre Muller wrote:
>>
>> Instead of adding a new command line option,
>> we might change this into a new command
>> call
>> set windows-os-tty on/off
>>
>> In the testsuite, this could be
>> automated by adding "-ex {set windows-os-tty on}"
>> to INTERNAL_GDBFLAGS.
>> This is what I do to run the testsuite on
>> msys for the "set interactive-mode on"
>> command that I added a while ago to resolve a similar problem.
>>
>> This would avoid adding a target specific command line option
>> and allow to move most of the code to mingw-hdep.c source
>> where it belongs as it really is mingw specific, no?
>
>
> Yeah, I agree, but I am worried that stdio handlers (such as stdout) should
> be set before any writes to them, so we should set the flag (cygwin_tty) at
> the early stage of GDB start up (before command 'set windows-os-tty on' is
> processed). If it is not a problem, I am fine.
>
> I am looking at Corinna's example to see how to detect GDB is running in
> Cygwin's TTY. If it works, probably we can get rid of this new GDB option
> completely.
As a data point, and I agree that avoiding any new option would be preferable,
in addition to -ex there is also -iex which is performed earlier in
the gdb startup process
(before symbol files are read, for example).
next prev parent reply other threads:[~2013-07-26 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 5:10 [PATCH 0/3] Test mingw32 GDB in cygwin Yao Qi
2013-07-25 5:10 ` [PATCH 1/3] New option --cygwin-tty Yao Qi
2013-07-25 7:34 ` Corinna Vinschen
2013-07-25 7:37 ` Pierre Muller
2013-07-25 7:55 ` Yao Qi
2013-07-25 8:18 ` Corinna Vinschen
2013-07-25 8:26 ` Corinna Vinschen
2013-07-25 9:05 ` Yao Qi
2013-07-25 10:20 ` Corinna Vinschen
2013-07-25 12:08 ` Yao Qi
2013-07-25 15:21 ` Corinna Vinschen
2013-07-26 19:40 ` Doug Evans [this message]
2013-07-25 5:10 ` [PATCH 2/3] Unbuffer stdout and stderr on windows Yao Qi
2013-07-25 5:10 ` [PATCH 3/3] native mingw32 gdb, eol format Yao Qi
2013-07-25 7:31 ` [PATCH 0/3] Test mingw32 GDB in cygwin Pierre Muller
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='CADPb22QfOzhV7r6QGVZ8y2DHTdTXA6MzaG3=CHZGq0A-rgz+ag@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
--cc=yao@codesourcery.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