Re: the redirected stdin/out/err for new console is wrong when the gdb's stdin/out/err is already redirected

[Eli Zaretskii <eliz@gnu.org>]

[Please use Reply All to reply, so that the list is CC'ed.]

> From: Roy Qu <royqh1979@gmail.com>
> Date: Sat, 3 Oct 2020 00:22:46 +0800
> 
> Eli Zaretskii <eliz@gnu.org> 于2020年10月2日周五 下午10:49写道：
> 
>  [Please use Reply All to reply, so that the list is CC'ed.]

Please do, you continue replying only to me, which requires me to
quote the entire message sent by you to the list, and also prevents
others from replying in a timely manner.

> 
>  > From: Roy Qu <royqh1979@gmail.com>
>  > Date: Fri, 2 Oct 2020 21:58:13 +0800
>  > 
>  >
>  https://stackoverflow.com/questions/30494945/createprocess-with-new-console-window-but-override-some-std-i-o-handles
>  
>  > 
>  > Point 1.You are right, NULL doesn't work under windows 7.
>  > So we need a better solution here.
> 
>  OK.
> 
>  > Point 2. When GDB's standard output is not redirected (started in console) , the inferior's ouput will
>  go to it's
>  > own console, not the gdb's console.
> 
>  Really?  I thought this happens only if you say
> 
>    (gdb) set new-console 1
> 
>  If I'm wrong, then where is the code which causes that other console
>  to be created for the inferior?
> 
> Yes. Can we add a check here to see if there should be a new console ?

Probably, but I hope someone else will explain how to do that.

And if we do have such a test, how will that affect the issue you
would like to solve?  Does the problem only happen when the inferior
has a separate console?