unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: emacs gdb subproccess ignores printf (stdout isn't flushed ?) on OS X
Date: Sun, 20 Feb 2005 23:51:20 +0100	[thread overview]
Message-ID: <8672e8beacc740604ebf814ed7a1a433@Web.DE> (raw)
In-Reply-To: <16a8b914050220111754b1cb75@mail.gmail.com>


Am 20.02.2005 um 20:17 schrieb Mike Garey:

> I've noticed that when using gdb under the carbon (Apple OS X) version
> of GNU Emacs 21.3.50.1, printf statements are not printed until after
> the program has terminated, even though the print statements contain a
> newline.  I can force them to print by modifying my source and adding
> "fflush(NULL);" after each printf statement, but I'd like to find out
> how to avoid this.

Hello!

Could you check process-connection-type? Is it nil, i.e.communication 
via pipes? Then try it with this:

         (setq process-connection-type t)

This makes shell work correct too!

--
Greetings

   Pete

The mathematician who pursues his studies without clear views of this 
matter, must often have the uncomfortable feeling that his paper and 
pencil surpass him in intelligence. (Ernst Mach)

  reply	other threads:[~2005-02-20 22:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20 19:17 emacs gdb subproccess ignores printf (stdout isn't flushed ?) on OS X Mike Garey
2005-02-20 22:51 ` Peter Dyballa [this message]
2005-02-20 23:08   ` suppressing gdb subprocess control characters? (was Re: emacs gdb subproccess ignores printf (stdout isn't flushed ?) on OS X) Mike Garey
2005-02-21  0:21     ` Peter Dyballa
     [not found] <mailman.814.1108929216.32256.help-gnu-emacs@gnu.org>
2005-02-22 14:46 ` emacs gdb subproccess ignores printf (stdout isn't flushed ?) on OS X Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=8672e8beacc740604ebf814ed7a1a433@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).