Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Gordon Prieur <Gordon.Prieur@Sun.COM>
To: gdb@sourceware.org
Subject: Question about when stdout is flushed in gdb/mi mode
Date: Tue, 19 Feb 2008 16:39:00 -0000	[thread overview]
Message-ID: <47BB0490.6070703@sun.com> (raw)

Hi,

    If I do several printf command before a breakpoint in normal
command line gdb, the stdout gets flushed prior to showing the stop
message in gdb. If I do the same thing in mi mode from a tty, I get
the same results. But if I do this from NetBeans (where gdb isn't
running in a tty), the output doesn't get flushed and hence doesn't
get shown before the stop.

    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?

Thanks,
Gordon


             reply	other threads:[~2008-02-19 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 16:39 Gordon Prieur [this message]
2008-02-19 17:52 ` Dave Korn
2008-02-19 18:20 ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47BB0490.6070703@sun.com \
    --to=gordon.prieur@sun.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox