Discussion:
[Bug mi/10079] Commands attached to a breakpoint do not execute in MI mode
P at draigBrady dot com
2015-10-15 00:09:29 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=10079

Pádraig Brady <P at draigBrady dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-10-15
CC| |P at draigBrady dot com
Ever confirmed|0 |1

--- Comment #6 from Pádraig Brady <P at draigBrady dot com> ---
As per the mail linked in comment #1 I see this when sourcing commands, where
the breakpoint commands aren't run unless an interactive prompt is displayed
first. I.E. if I pass `--eval-command='source breakpoint_file_with_commands'
--eval-command=run` the commands associated with a breakpoint aren't run, while
if I issue the "run" from the interactive prompt they are.
--
You are receiving this mail because:
You are on the CC list for the bug.
P at draigBrady dot com
2015-10-15 00:14:56 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=10079

Pádraig Brady <P at draigBrady dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Target|i686-pc-linux-gnu |
Component|mi |breakpoints
Host|i686-pc-linux-gnu |
Summary|Commands attached to a |Commands attached to a
|breakpoint do not execute |breakpoint do not execute
|in MI mode |without an interactive
| |prompt
Build|i686-pc-linux-gnu |
--
You are receiving this mail because:
You are on the CC list for the bug.
edaskel at att dot net
2018-08-02 17:51:07 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=10079

Jeff Trull <edaskel at att dot net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |edaskel at att dot net

--- Comment #7 from Jeff Trull <edaskel at att dot net> ---
Created attachment 11160
--> https://sourceware.org/bugzilla/attachment.cgi?id=11160&action=edit
minimal test case

This is the source code I'm debugging
--
You are receiving this mail because:
You are on the CC list for the bug.
edaskel at att dot net
2018-08-02 17:51:56 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=10079

--- Comment #8 from Jeff Trull <edaskel at att dot net> ---
Created attachment 11161
--> https://sourceware.org/bugzilla/attachment.cgi?id=11161&action=edit
The gdb commands I expect to run without pausing for terminal input
--
You are receiving this mail because:
You are on the CC list for the bug.
edaskel at att dot net
2018-08-02 17:53:57 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=10079

--- Comment #9 from Jeff Trull <edaskel at att dot net> ---
Sorry, attachments came before explanation :-/

I have a problem that I believe to be the same as this one. I've attached a MWE
and a set of commands for review and reproduction.

Description:
a "continue" inside a set of commands for a breakpoint is not obeyed until the
user hits enter. Furthermore it only happens if I give the run command on the
command line vs typing it inside gdb.

My command line is: gdb -ex 'source test.gdb' -ex run mwe

where "mwe" is built from the first attachment, and "test.gdb" are the commands
in the second one.

What I expect to happen: when we encounter breakpoint 2, the commands, the last
of which is a "c", should be run and the program should continue
What actually happens: gdb pauses until I hit "return", then finishes the
program

If instead I leave off the second "ex" from the command line, and just type
"run" inside gdb, it works fine, and if I put the "run" at the end of the
sourced file, that also works fine.
--
You are receiving this mail because:
You are on the CC list for the bug.
Loading...