From: "Jon Beniston" <jon@beniston.com>
To: <gdb@sourceware.org>
Cc: <palves@redhat.com>, <jonah@kichwacoders.com>
Subject: Re: new-ui and Windows
Date: Tue, 08 Aug 2017 14:53:00 -0000 [thread overview]
Message-ID: <008b01d31056$1e7348e0$5b59daa0$@beniston.com> (raw)
>I am looking to support the new-ui functionality[1] for Eclipse CDT on
> Windows [2].
> I would like to know if new-ui is supposed to work on Windows with
> mingw host?
I'm just looking at this as well, but for a Cygwin based GDB, rather than
mingw.
>> The new-ui attempts to open a tty with
>> top.c:open_terminal_stream() which calls open(). On Windows, AFAIK,
>> this can only open a normal file.
>What kind of file would you like to pass to gdb? My original idea
>was that on Windows you'd pass down the path to a bidirectional/duplex
>named pipe, and things would Just Work (TM). Doesn't open() work on
>such named pipe paths? If not, then the "struct serial" abstraction
>seems to know about named pipes already (ser-mingw.c), so maybe it'd work
>to adjust the new-ui code to use serial_open instead.
I think using serial_open would be quite handy, as presumably this would
allow a TCP connection to Eclipse?
If so, I suspect this would be a lot easier to support in Eclipse, as there
would be no need for JNI code to interface with Cygwin PTYs or Windows named
pipes - and it even could be the same Java code for MacOS and Linux too.
Do you see any problems with that?
Cheers,
Jon
next reply other threads:[~2017-08-08 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 14:53 Jon Beniston [this message]
2017-08-08 15:09 ` Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2017-05-15 12:39 Jonah Graham
2017-05-15 19:18 ` Eli Zaretskii
2017-05-15 22:49 ` Pedro Alves
2017-05-16 8:52 ` Jonah Graham
2017-05-16 18:34 ` Eli Zaretskii
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='008b01d31056$1e7348e0$5b59daa0$@beniston.com' \
--to=jon@beniston.com \
--cc=gdb@sourceware.org \
--cc=jonah@kichwacoders.com \
--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