Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Shaun Jackman <sjackman@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: arm-elf-run and ANSI escape sequences
Date: Fri, 27 May 2005 19:16:00 -0000	[thread overview]
Message-ID: <20050527191627.GB18636@nevyn.them.org> (raw)
In-Reply-To: <7f45d9390505271202e8db5bf@mail.gmail.com>

On Fri, May 27, 2005 at 12:02:30PM -0700, Shaun Jackman wrote:
> First off, let me just say how impressed I am with the ARM simulator!
> It astounds me that I can run a binary intended for my embedded
> platform with no modification on my development machine.
> 
> I'm running an ARM binary using arm-elf-run that makes use of ANSI
> escape sequences to control the terminal emulator (konsole in my
> case). Clear screen, "\33[2J", works fine. But the combination of save
> cursor, "\33[s", and restore cursor, "\33[u" does not. If the answer
> is "That does not work." that'd be fine. I'm just a little curious
> where it's gone wrong. I figured the escape sequences would be passed
> right on through to the terminal emulator, and no-one would ever know
> the binary's being run by an ARM simulator. If I compile the
> application natively (using gcc instead of arm-elf-gcc) and run it,
> save cursor and restore cursor work as expected.
> 
> I no very little (ok, nothing) about the internals of gdb, but if gdb
> sets up a pseudo-teletype for the child process, perhaps the
> save-cursor function does not work with this pseudo-teletype?

GDB doesn't use ptys.  You'll need to find out what is actually being
written to the screen.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-27 19:16 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 [this message]
2005-05-27 23:35   ` Shaun Jackman
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=20050527191627.GB18636@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=sjackman@gmail.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