From: Matt Rice <ratmice@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: David Boles <boles@ieee.org>, GDB <gdb@sourceware.org>
Subject: Re: repeat command on return after issuing guile command
Date: Mon, 01 May 2017 11:20:00 -0000 [thread overview]
Message-ID: <CACTLOFr-hRC14+He+KrdmFxx28Bo2rvSw75o15fLddR=v+SWxw@mail.gmail.com> (raw)
In-Reply-To: <83wpa1k9ab.fsf@gnu.org>
On Sun, Apr 30, 2017 at 12:03 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: David Boles <boles@ieee.org>
>> Date: Fri, 28 Apr 2017 22:50:18 -0500
>>
>> 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.
>
> I cannot reproduce this with GDB 7.12 built with Guile 2.0.X. I tried
> this:
>
> (gdb) apropos file
> ... long list of commands ...
> (gdb) <press RET>
> ... the same long list of commands ...
> (gdb) guile (display (+ 20 3)) (newline)
> 23
> (gdb) apropos file
> ... long list of commands ...
> (gdb) <press RET>
> ... the same long list of commands ...
>
> So it seems to work as expected for me. Can you show a recipe that
> exhibits the problem on your system?
One thing that I can think of is if the guile script being executed
causes the program to continue,
which then hits a breakpoint which has "commands" associated with it,
the call to prevent_dont_repeat in
breakpoint.c (bpstat_do_actions_1), could have some clobbering effect
messes with the repeat.
I cannot seem reproduce such behavior though
using the following foo.gdb:
set breakpoint pending on
break foo
commands 1
print "foo"
end
guile (use-modules (gdb))
guile (execute "start")
guile (execute "cont")
$ echo "void foo() {}; int main() { while (1) foo(); return 0; }" |
gcc -g -x c - && gdb -quiet ./a.out -ex 'source foo.gdb'
Reading symbols from ./a.out...done.
Breakpoint 1 at 0x4004aa: file <stdin>, line 1.
Breakpoint 1, foo () at <stdin>:1
1 in <stdin>
$1 = "foo"
(gdb) guile (execute "cont")
Breakpoint 1, foo () at <stdin>:1
1 in <stdin>
$2 = "foo"
(gdb)
Breakpoint 1, foo () at <stdin>:1
1 in <stdin>
$3 = "foo"
(gdb)
next prev parent reply other threads:[~2017-05-01 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 3:50 David Boles
2017-04-30 19:04 ` Eli Zaretskii
2017-05-01 11:20 ` Matt Rice [this message]
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='CACTLOFr-hRC14+He+KrdmFxx28Bo2rvSw75o15fLddR=v+SWxw@mail.gmail.com' \
--to=ratmice@gmail.com \
--cc=boles@ieee.org \
--cc=eliz@gnu.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