From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14462 invoked by alias); 27 May 2005 19:16:32 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 14452 invoked by uid 22791); 27 May 2005 19:16:29 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 27 May 2005 19:16:29 +0000 Received: from drow by nevyn.them.org with local (Exim 4.50) id 1DbkJn-0004rz-30; Fri, 27 May 2005 15:16:27 -0400 Date: Fri, 27 May 2005 19:16:00 -0000 From: Daniel Jacobowitz To: Shaun Jackman Cc: gdb@sources.redhat.com Subject: Re: arm-elf-run and ANSI escape sequences Message-ID: <20050527191627.GB18636@nevyn.them.org> Mail-Followup-To: Shaun Jackman , gdb@sources.redhat.com References: <7f45d9390505271202e8db5bf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f45d9390505271202e8db5bf@mail.gmail.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-05/txt/msg00353.txt.bz2 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