public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] PR17525 - breakpoint commands not executed when program run, from -x script
Date: Wed, 14 Jan 2015 13:27:00 -0000	[thread overview]
Message-ID: <54B66EA5.6020301@redhat.com> (raw)
In-Reply-To: <20150114112942.GK8167@adacore.com>

On 01/14/2015 11:29 AM, Joel Brobecker wrote:

> ... this is an issue which was identified as a regression for
> 7.8 and 7.9. I suggest we backport them to both branches, if
> you agree, and once the patch is pushed to master, I volunteer
> doing so if that saves you a bit of time.

Nah, I already needed to push
  https://sourceware.org/ml/gdb-patches/2015-01/msg00372.html
to the branch, and as this one is going to 7.8, I pushed
that one in as well, as it's kind of related.

Below's what I pushed to master, 7.9 and 7.8.  I removed a
couple of unnecessary lines from the .exp and .gdb files.

> Regarding GDBFLAGS, I'm wondering whether this might be one of
> those globals that we should be restoring at the start of each
> testcase (via gdb_init)...

Hmm, that might be a good idea.

----------------
[PATCH] PR17525 - breakpoint commands not executed when program run from -x script

Executing a gdb script that runs the inferior (from the command line
with -x), and has it hit breakpoints with breakpoint commands that
themselves run the target, is currently broken on async targets
(Linux, remote).

While we're executing a command list or a script, we force the
interpreter to be sync, which results in some functions nesting an
event loop and waiting for the target to stop, instead of returning
immediately and having the top level event loop handle the stop.

The issue with this bug is simply that bpstat_do_actions misses
checking whether the interpreter is sync.  When we get here, in the
case of executing a script (or, when the interpreter is sync), the
program has already advanced to the next breakpoint, through
maybe_wait_sync_command_done.  We need to process its breakpoints
immediately, just like with a sync target.

Tested on x86_64 Fedora 20.

gdb/
2015-01-14  Pedro Alves  <palves@redhat.com>

	PR gdb/17525
	* breakpoint.c: Include "interps.h".
	(bpstat_do_actions_1): Also check whether the interpreter is
	async.

gdb/testsuite/
2015-01-14  Pedro Alves  <palves@redhat.com>
	    Joel Brobecker  <brobecker@adacore.com>

	PR gdb/17525
	* gdb.base/bp-cmds-execution-x-script.c: New file.
	* gdb.base/bp-cmds-execution-x-script.exp: New file.
	* gdb.base/bp-cmds-execution-x-script.gdb: New file.
---
 gdb/ChangeLog                                      |  7 ++
 gdb/testsuite/ChangeLog                            |  8 +++
 gdb/breakpoint.c                                   |  4 +-
 .../gdb.base/bp-cmds-execution-x-script.c          | 35 ++++++++++
 .../gdb.base/bp-cmds-execution-x-script.exp        | 75 ++++++++++++++++++++++
 .../gdb.base/bp-cmds-execution-x-script.gdb        | 20 ++++++
 6 files changed, 147 insertions(+), 2 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/bp-cmds-execution-x-script.c
 create mode 100644 gdb/testsuite/gdb.base/bp-cmds-execution-x-script.exp
 create mode 100644 gdb/testsuite/gdb.base/bp-cmds-execution-x-script.gdb

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index b84ffc8..648b341 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,12 @@
 2015-01-14  Pedro Alves  <palves@redhat.com>

+	PR gdb/17525
+	* breakpoint.c: Include "interps.h".
+	(bpstat_do_actions_1): Also check whether the interpreter is
+	async.
+
+2015-01-14  Pedro Alves  <palves@redhat.com>
+
 	PR cli/17828
 	* infrun.c (reinstall_readline_callback_handler_cleanup): Don't
 	reinstall if the interpreter is sync.
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 7e74501..2f747b5 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,4 +1,12 @@
 2015-01-14  Pedro Alves  <palves@redhat.com>
+	    Joel Brobecker  <brobecker@adacore.com>
+
+	PR gdb/17525
+	* gdb.base/bp-cmds-execution-x-script.c: New file.
+	* gdb.base/bp-cmds-execution-x-script.exp: New file.
+	* gdb.base/bp-cmds-execution-x-script.gdb: New file.
+
+2015-01-14  Pedro Alves  <palves@redhat.com>

 	PR cli/17828
 	* gdb.base/batch-preserve-term-settings.c: New file.
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index c64c2a9..af0c2cf 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -66,7 +66,7 @@
 #include "skip.h"
 #include "ax-gdb.h"
 #include "dummy-frame.h"
-
+#include "interps.h"
 #include "format.h"

 /* readline include files */
@@ -4635,7 +4635,7 @@ bpstat_do_actions_1 (bpstat *bsp)

       if (breakpoint_proceeded)
 	{
-	  if (target_can_async_p ())
+	  if (interpreter_async && target_can_async_p ())
 	    /* If we are in async mode, then the target might be still
 	       running, not stopped at any breakpoint, so nothing for
 	       us to do here -- just return to the event loop.  */
diff --git a/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.c b/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.c
new file mode 100644
index 0000000..f7101b6
--- /dev/null
+++ b/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.c
@@ -0,0 +1,35 @@
+/* This testcase is part of GDB, the GNU debugger.
+
+   Copyright 2015 Free Software Foundation, Inc.
+
+   This program is free software; you can redistribute it and/or modify
+   it under the terms of the GNU General Public License as published by
+   the Free Software Foundation; either version 3 of the License, or
+   (at your option) any later version.
+
+   This program is distributed in the hope that it will be useful,
+   but WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+   GNU General Public License for more details.
+
+   You should have received a copy of the GNU General Public License
+   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
+
+int
+increment (int i)
+{
+  return i + 1;
+}
+
+#define N_INCR 20
+
+int
+main (void)
+{
+  int val = 1;
+  int j;
+
+  for (j = 0; j < N_INCR; j++)
+    val = increment (val);
+  return val == N_INCR;
+}
diff --git a/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.exp b/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.exp
new file mode 100644
index 0000000..e75a4fd
--- /dev/null
+++ b/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.exp
@@ -0,0 +1,75 @@
+# Copyright 2015 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
+
+# Test that GDB isn't silent if it fails to remove a breakpoint from
+# the main program, independently of whether the program was loaded
+# with "file PROGRAM" or directly from the command line with "gdb
+# PROGRAM".
+
+# Test that execution commands in a GDB script file run through -x
+# work as expected.  Specifically, the scripts creates a breakpoint
+# that has "continue" in its command list, and then does "run".
+
+standard_testfile
+
+if {[build_executable "failed to prepare" $testfile $srcfile debug]} {
+    return -1
+}
+
+set x_file ${srcdir}/${subdir}/$testfile.gdb
+
+global GDBFLAGS
+set saved_gdbflags $GDBFLAGS
+
+# Run the test proper.
+
+proc test {} {
+    global inferior_exited_re
+    global binfile
+    global gdb_prompt
+    global saved_gdbflags GDBFLAGS
+    global x_file
+
+    gdb_exit
+
+    set GDBFLAGS "$GDBFLAGS -x $x_file $binfile"
+
+    set GDBFLAGS $saved_gdbflags
+    append GDBFLAGS " -ex \"set height unlimited\""
+    append GDBFLAGS " -x \"$x_file\""
+    append GDBFLAGS " --args \"$binfile\""
+
+    set test "run to end"
+
+    gdb_exit
+    set res [gdb_spawn]
+    if { $res != 0} {
+	fail $test
+	return -1
+    }
+
+    gdb_test_multiple "" $test {
+	-re "$inferior_exited_re normally.*$gdb_prompt $" {
+	    pass $test
+	}
+	-re "Don't know how to run.*$gdb_prompt $" {
+	    unsupported $test
+	}
+    }
+}
+
+test
+
+set GDBFLAGS $saved_gdbflags
diff --git a/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.gdb b/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.gdb
new file mode 100644
index 0000000..6d5b4e4
--- /dev/null
+++ b/gdb/testsuite/gdb.base/bp-cmds-execution-x-script.gdb
@@ -0,0 +1,20 @@
+# Copyright 2015 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
+
+break increment
+commands
+   cont
+end
+run
-- 
1.9.3


      reply	other threads:[~2015-01-14 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 19:00 Pedro Alves
2015-01-14 11:29 ` Joel Brobecker
2015-01-14 13:27   ` Pedro Alves [this message]

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=54B66EA5.6020301@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).