RE: [PATCH]Fix that GDB will get hang on Windows when using pipe to get stdout and stderr from stub

Hi Eli,

Can you help to review this proposal? The GDB trunk also has this issue.
Thanks.

BR,
Terry

> -----Original Message-----
> From: gdb-patches-owner <at> sourceware.org [mailto:gdb-patches-
> owner <at> sourceware.org] On Behalf Of Terry Guo
> Sent: Tuesday, June 26, 2012 9:13 AM
> To: gdb-patches <at> sourceware.org
> Cc: eliz <at> gnu.org; Joey Ye; Matthew Gretton-Dann; 'Pedro Alves';
> daniel.jacobowitz <at> gmail.com
> Subject: [PATCH]Fix that GDB will get hang on Windows when using pipe
> to get stdout and stderr from stub
> 
> Hi,
> 
> I noticed a cross-built MINGW arm-none-eabi GDB will get hang on
> Windows
> when use pipe to get stderr and stdout from stub. The command used to
> start
> stub in GDB is "target extended-remote |
> stub-that-write-stderr-before-stdout". For my case, after send
> "$vFlashDone#ea" to stub, GDB get hang. The GDB source show that GDB
> will
> keep waiting for ACK message from stdout of stub, after send the packet.
> Unfortunately my stub will write some kind of log information into