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

[Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>]

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

> 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?

> So if gdb's STDOUT is redirected,
> I think the inferior's output should go to it's own console ,too.

I'm asking whether we always want that.  I hope others who have
experience with running GDB on MS-Windows will chime in and comment on
this part.

Thanks.