public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: arm-elf-run and ANSI escape sequences
Date: Fri, 27 May 2005 23:35:00 -0000	[thread overview]
Message-ID: <7f45d9390505271635729a687e@mail.gmail.com> (raw)
In-Reply-To: <20050527191627.GB18636@nevyn.them.org>

On 5/27/05, Daniel Jacobowitz <drow@false.org> wrote:
> GDB doesn't use ptys.  You'll need to find out what is actually being
> written to the screen.

Thanks for the quick reply, Daniel. It seems that my trouble is due to
the output from the simulator being line buffered. I've checked that
this line buffering is not being done by the ARM binary being
executed. It appears to be done by GDB (arm-elf-run) or its terminal,
or...

My quick test is...
	fputs("Hello, ", stdout);
	getchar();
	puts("world!");

The getchar() flushes stdout, but nothing is displayed. Upon pushing
Enter, "Hello, world!" is displayed.

Do you have an idea as to which component in the output stream is
doing the buffering?

Thanks,
Shaun

  reply	other threads:[~2005-05-27 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 19:02 Shaun Jackman
2005-05-27 19:16 ` Daniel Jacobowitz
2005-05-27 23:35   ` Shaun Jackman [this message]
2005-05-28  0:12     ` 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=7f45d9390505271635729a687e@mail.gmail.com \
    --to=sjackman@gmail.com \
    --cc=gdb@sources.redhat.com \
    /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).