From: David Boles <boles@ieee.org>
To: gdb@sourceware.org
Subject: repeat command on return after issuing guile command
Date: Sat, 29 Apr 2017 03:50:00 -0000 [thread overview]
Message-ID: <18055C3E-BBEA-4CBD-A12A-511B46D1B2AB@ieee.org> (raw)
I have recently been learning to use the guile mechanism for extending gdb’s capabilities - very powerful. One thing that I have noticed is that after a “guile (…)” command is issued, the normal behavior of gdb re-performing the last command executed if you just hit enter is disabled. This applies to even native gdb commands like “next” or “step” - which is quite painful.
I have observed this with versions 7.10.x and 7.12.1.
Any insights would be appreciated.
Thx,
- db
next reply other threads:[~2017-04-29 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 3:50 David Boles [this message]
2017-04-30 19:04 ` Eli Zaretskii
2017-05-01 11:20 ` Matt Rice
2017-05-01 16:37 ` David Boles
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=18055C3E-BBEA-4CBD-A12A-511B46D1B2AB@ieee.org \
--to=boles@ieee.org \
--cc=gdb@sourceware.org \
/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