From: Daniel Jacobowitz <drow@mvista.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: operate-and-get-next is off by one
Date: Sun, 21 Apr 2002 12:52:00 -0000 [thread overview]
Message-ID: <20020421155208.A25490@nevyn.them.org> (raw)
In-Reply-To: <87wuv0rgs9.fsf@creche.redhat.com>
On Sun, Apr 21, 2002 at 01:30:14PM -0600, Tom Tromey wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>
> Daniel> It appears to be "operate-and-get-command-after-next" right
> Daniel> now. It's skipping every other command...
>
> What system? How are you invoking gdb?
>
> I updated and rebuilt gdb from scratch on x86 Linux (RHL 6.2).
> operate-and-get-next seems to work fine in my simple test:
>
> p 1
> p 2
> p 3
> C-n C-n C-n
> C-o C-o
You mean C-p, I assume...
> If you can tell me a simple way to reproduce the problem I will look
> at it.
I can no longer reproduce the exact sequence, unfortunately. It was
an interaction with 'commands'; I was trying to reset the commands of
a breakpoint. Now when I try it simply skips all the '>' prompts, and
leaves the command after 'commands' at the (gdb) prompt after I type
'end'. It would be very convenient if C-o worked at the > prompt also,
since everything you type there makes it into the command history.
If I reproduce the original problem again I'll let you know.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-21 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 22:02 Daniel Jacobowitz
2002-04-21 12:34 ` Tom Tromey
2002-04-21 12:52 ` Daniel Jacobowitz [this message]
2002-04-21 12:57 ` Tom Tromey
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=20020421155208.A25490@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=tromey@redhat.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