This is the mail archive of the gdb@sourceware.cygnus.com mailing list for the GDB project. See the GDB home page for more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: keeping commands out of the history

> No, I'm talking about both the command and value history.  I want to
> be able to send commands to and receive output from gdb without it
> having any impact on what someone typing commands at the prompt sees.
> Currently, if I type 'next' at the gdb prompt, it gets executed and my
> hooks do, e.g., 'info registers', and put the output in a different buffer.
> If I then type '<RET>' at the gdb prompt, it runs 'info registers' again,
> not 'next'.  I want to it run 'next'.

Perhaps what you really want is for _hooks_ to be kept out of the value
history. That sounds to me like a good thing, if it isn't already true.

-- 
Todd Whitesel
toddpw @ wrs.com