Question about when stdout is flushed in gdb/mi mode

[Dave Korn]

On 19 February 2008 16:32, Gordon Prieur wrote:

>     Looking at the gdb options, I don't see anyway of forcing a
> flush of stdout. Since stdout isn't a variable and libc is typically
> optimized without debug information, neither "fflush(stdout)" nor
> "fflush(&__iob[1])" work. Is there anyway to force gdb to flush
> stdout when it stops?

  You could always rely on the default behaviour of "fflush (NULL)", if you
don't mind other descriptors getting flushed too.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....