| Re: [cdt-dev] Bug 159803: PTY in console mode on Windows |
|
Ok, thanks for all the replies and trying to reproduce my findings. Even with MinGW from mingw.org and linking the standard libraries statically I encounter strange behavior: -
On Windows 10 64bit the aforementioned fsdf -
On Windows 7 64bit I get a new sympthom, the input is duplicated in some cases:
o
If entered repeatedly “a” (without quotes) sometimes becomes “a” and sometimes it is duplicated “aa” I guess something on my machines is really strange. Toni mentioned, earlier in the conversation, that it will be ok to terminate the input stream by sending the EOT character (value 4) and that’s what I actually wanted to
figure out. I think Marc-André can continue with that. Or what would be even better if the patch at
https://git.eclipse.org/r/#/c/55511/ could be tested for WinPTY in console mode. Apparently, I’m currently stuck on that end – I’ll try to figure out what’s wrong on my site, but don’t know whether I can expect
progress soon. Thanks for the help! Thomas From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Leherbauer, Anton (Toni) I have no explanation for the ‘f’ character at the beginning of the output (I don’t see it on Windows 7), but it is no surprise that winpty in console mode has some issues (https://bugs.eclipse.org/bugs/show_bug.cgi?id=419391#c36). That’s why it is an experimental feature. winpty is primarily intended for use with a terminal emulator (like org.eclipse.tm.terminal). The process terminates on Ctrl+Z immediately, because the Eclipse console does not send a literal Ctrl+Z, but closes the pty output stream. In the case of winpty, this destroys the winpty-agent process and its children. This is a limitation of the winpty API, but it is no problem when using it with a terminal. Toni From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Corbat Thomas I started over on Windows 10 64bit and MinGW from nuwen.net. It got a bit bizarre. I created a program (code see below) that reads a character from cin and and prints it, together with endl to cout.
I do that continuously in a while loop. As always, this works on an external console and in CDT as expected. Input: asdf<Enter> Output: a s d f Now, when I enable winpty in console mode I get the following output with the same input: fsdf Yes, it is actually starting with an ‘f’ and I don’t get linebreaks. Honestly, I would not have believed that if hadn’t seen it myself. When I terminate the Input with ctrl+z, the program terminates
without finishing properly, i.e. output after the while loop is omitted. Here is the code I run. I’d be happy to hear that it contained undefined behavior and that was the reason for my observations. #include <iostream> I’ll give MinGW from mingw.org a try. Regards Thomas From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Leherbauer, Anton (Toni) I just tried again with the C++ hello world including iostream, but it works for me – as long as I specify the correct PATH. The difference between the C and C++ versions of hello world is that the latter requires 2 mingw DLLs to run. You could also try building/linking the C++ code with -static-libgcc -static-libstdc++. That makes it a statically linked executable. I am using the gcc from
www.mingw.org. Cheers, Toni From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Corbat Thomas I thought of that too. But, then I wouldn’t be able to execute it on console. And it also works if I don’t set the -Dorg.eclipse.cdt.core.winpty_console_mode=true flag for my child CDT. Furthermore,
I figured out that it is only an issue with iostream, but it works with the C hello world example including stdio. I just tried MinGW from nuwen.net (version 5.1). It works neither. Perhaps I need to clean up my PATHs for MinGW. Regards Thomas From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Leherbauer, Anton (Toni) Hi Thomas, I assume your program fails to load the DLLs it depends on. You need to add the appropriate PATH in the run config environment. Did you try running the program without PTY within Eclipse? I’d expect the same failure there as well. Sending EOT before close should work with winpty as well. HTH, Toni From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Corbat Thomas Hi Toni Thanks for checking! I’m working on Windows 7 64bit too. It might depend on the compiler or the standard library implementation though. Currently, I use MinGW g++ 4.8.1 from mingw-builds (http://sourceforge.net/projects/mingwbuilds/). My test program was very small: main function with an endless while loop. After checking again I figured out that it depends on whether I have an include to iostream or not. With include to iostream
the program crashes (in CDT with PTY, not in an external console). Without that include it works properly, as far as I can tell. I actually wanted to check whether the PTY implementation can cope with sending EOT before closing the stream or not. Unfortunately, I cannot try it with the current behavior of my system. I’ll try
another compiler. Kind Regards Thomas From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Leherbauer, Anton (Toni) Hi Thomas, using winpty in console mode on Windows has always been an experimental feature which can only be enabled with -Dorg.eclipse.cdt.core.winpty_console_mode=true. Anyway, I just tried it with a hello world project and some other programs. It seems to work for me (Windows 7 64-bit). Please provide details about the target program, how you build it and on which version of Windows you run it. Thanks, Toni From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Corbat Thomas Hi Marc-André and I are currently investigating the ctrl-D issue (Bug 159803). While trying to
figure out whether a possible fix would have some issues on Windows I tried to use the PTY in console mode, explicitly enabled with -Dorg.eclipse.cdt.core.winpty_console_mode=true. This resulted in my target program to terminate immediately, regardless of
whether it contained I/O or not. Has anybody recently used the PTY in console mode on Windows successfully? I remember that the corresponding flag in the run configuration had been disabled on Windows for quite some time (I don’t know whether it had
been active at any time at all), so it would have been required to set this explicitly using the system property mentioned above. Any input on that issue is welcome! Regards Thomas |