Re: Console window command line recall

[Fernando Nasser <fnasser at cygnus dot com>]

Grant Edwards wrote:
> 
> On Thu, Sep 14, 2000 at 03:28:27PM +0000, Fernando Nasser wrote:
> 
> > Cut-and-paste problems to/from the GUI console sound familiar.
> 
> Unfortunately, due to lack of a way to save "print" or "x"
> output to a file, I often have to cut/paste the output of
> "print" to a file for automated analysis.  It still works using
> non-GUI mode, so I can run that way when I need to save data
> for later analysis.
> 

I believe this is a Tk problem.  We do need to upgrade...


> > With regards to the history problem, please try it with a
> > command that does not auto-increment.
> >
> > You may be seeing a side-effect of the trick gdb plays with
> > these commands so you can just hit ENTER and have it show the
> > next address.
> 
> You're right, It only seems to happen with auto-incrementing
> commands like "x", and for the disassemble command, it only
> recalls the first parameter:
> 
> (gdb) disassemble 0 16
> Dump of assembler code from 0x0 to 0x10:
>   ...
> 
> [up-arrow][enter]
> 
> (gdb) disassemble 0
> Error: No function contains specified address.
> 
> > Does this happen in the normal (non GUI) console as well?
> 
> Nope. When run with '-nw', an up-arrow recalls the entire
> command line for all commands (that's how I got into the habit
> of using an "x" command and a repeated [up-arrow][enter] to
> monitor the value of something while I poke at the target
> hardware.
> 

OK, so that is a bug then.  Goes to the list.

In the meanwhile, why don't you do like I do when I want to avoid the
auto-incerment of the address:

define mx
x/8x 0xff000000
end

There will be no auto-increment in this case.





-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299