If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
STDERR
Hi All,
W7 and W10 Command prompt. wfreerdp: https://cloudbase.it/freerdp-for-win...ightly-builds/ Am I correct that you can only see the STDERR if you redirect it to a file? For example: wfreerdp.exe /help b.txt 2&1 The does not work: wfreerdp.exe /help 2&1 Hmmmm. Perhaps I am spoiled by bash? Am I missing something? I write a bunch in Perl 6. I am constantly outputting to STDERR in Linux. I presume as I start to write more for Windows, I will have to stay away from STDERR. Many thanks, -T |
Ads |
#2
|
|||
|
|||
STDERR
T wrote:
The does not work: wfreerdp.exeÂ* /help 2&1 If you don't redirect anything, then both stdout and stderr go to the console, so normally if you want to redirect all output you'd do as you tried command 1file.txt 2&1 if that works for other commands, maybe wfreerdp is just weird and opens itself a separate console? |
#3
|
|||
|
|||
STDERR
On 12/13/18 9:52 AM, Andy Burns wrote:
T wrote: The does not work: wfreerdp.exeÂ* /help 2&1 If you don't redirect anything, then both stdout and stderr go to the console, so normally if you want to redirect all output you'd do as you tried command 1file.txt 2&1 if that works for other commands, maybe wfreerdp is just weird and opens itself a separate console? That was my understanding too. I am at a loss as to why wfreerdp is acting so weird. wfreerdp will open a UI with "wfreerdp /v:xxx.yyy.zzz.qqqort", providing you get the IP and port correct. But if you blow it (what me? NEVER!), you don't get any errors back at the command window. |
#4
|
|||
|
|||
STDERR
T wrote: you don't get any errors back at the command window. check %errorlevel% instead? |
#5
|
|||
|
|||
STDERR
On 13/12/2018 17:43, T wrote:
Hi All, W7 and W10 Command prompt. wfreerdp: https://cloudbase.it/freerdp-for-win...ightly-builds/ Am I correct that you can only see the STDERR if you redirect it to a file?Â* For example: Â*Â*Â* wfreerdp.exeÂ* /help b.txt 2&1 The does not work: wfreerdp.exeÂ* /help 2&1 Hmmmm.Â* Perhaps I am spoiled by bash?Â* Am I missing something? I write a bunch in Perl 6.Â* I am constantly outputting to STDERR in Linux.Â* I presume as I start to write more for Windows, I will have to stay away from STDERR. Many thanks, -T This seems to be a well known error: https://superuser.com/questions/1251...iling-silently |
#6
|
|||
|
|||
STDERR
On 12/13/18 11:16 AM, MikeS wrote:
On 13/12/2018 17:43, T wrote: Hi All, W7 and W10 Command prompt. wfreerdp: https://cloudbase.it/freerdp-for-win...ightly-builds/ Am I correct that you can only see the STDERR if you redirect it to a file?Â* For example: Â*Â*Â*Â* wfreerdp.exeÂ* /help b.txt 2&1 The does not work: wfreerdp.exeÂ* /help 2&1 Hmmmm.Â* Perhaps I am spoiled by bash?Â* Am I missing something? I write a bunch in Perl 6.Â* I am constantly outputting to STDERR in Linux.Â* I presume as I start to write more for Windows, I will have to stay away from STDERR. Many thanks, -T This seems to be a well known error: https://superuser.com/questions/1251...iling-silently Thank you. I thought I was losing my mind! |
#7
|
|||
|
|||
STDERR
On 12/13/18 10:24 AM, Andy Burns wrote:
T wrote: you don't get any errors back at the command window. check %errorlevel% instead? It is a bug |
#8
|
|||
|
|||
STDERR
T wrote:
On 12/13/18 10:24 AM, Andy Burns wrote: T wrote: you don't get any errors back at the command window. check %errorlevel% instead? It is a bug You might be able to use sysinternals Handle or Process Explorer to figure out what files it has open. Whether they're standard spigots or something else. Paul |
#9
|
|||
|
|||
STDERR
On 12/13/18 12:45 PM, Paul wrote:
T wrote: On 12/13/18 10:24 AM, Andy Burns wrote: T wrote: you don't get any errors back at the command window. check %errorlevel% instead? It is a bug You might be able to use sysinternals Handle or Process Explorer to figure out what files it has open. Whether they're standard spigots or something else. Â*Â* Paul Just running the program name by itself is suppose to trigger /help, but it is a bug that it acts so weird. I am trying to run down the bug to sign up for it. The program does work if you give it a good /v:IPort on the run line. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|