From: Todd Sabin <tastas@home.com>
To: tromey@cygnus.com
Cc: gdb@cygnus.com
Subject: Re: keeping commands out of the history
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <199903062105.QAA16766@banzai3.insignia.org> (raw)
In-Reply-To: <87u2vz2h5d.fsf@cygnus.com>
> >>>>> "Todd" == Todd Sabin <tastas@home.com> writes:
>
> Todd> This sounds good, but I also want to do 'info registers',
> Todd> 'where', and probably 'info breakpoints' in the future, so I'm
> Todd> really looking for something a little more general.
>
> I don't think any of these add to the value history.
> Or was that not what you were asking for?
>
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'.
Todd
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 Todd Sabin
1999-04-01 0:00 ` Todd Whitesel
1999-04-01 0:00 ` Todd Sabin
1999-04-01 0:00 ` Jim Blandy
1999-04-01 0:00 ` Todd Sabin
1999-04-01 0:00 ` Todd Whitesel
[not found] ` <199903060659.BAA13499.cygnus.gdb@banzai3.insignia.org>
1999-04-01 0:00 ` Tom Tromey
1999-04-01 0:00 ` Todd Sabin [this message]
1999-04-01 0:00 ` Todd Whitesel
1999-04-01 0:00 ` Todd Sabin
1999-04-01 0:00 ` Todd Whitesel
[not found] ` <199903060638.WAA29974.cygnus.gdb@alabama.wrs.com>
1999-04-01 0:00 ` Tom Tromey
1999-04-01 0:00 ` Todd Whitesel
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=199903062105.QAA16766@banzai3.insignia.org \
--to=tastas@home.com \
--cc=gdb@cygnus.com \
--cc=tromey@cygnus.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