From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA] Testcase for bug report 11531
Date: Fri, 23 Apr 2010 16:41:00 -0000 [thread overview]
Message-ID: <000301cae303$d6d068b0$84713a10$@muller@ics-cnrs.unistra.fr> (raw)
Test case for the newly discovered
problem with the old CANNOT_STEP_HW_WATCHPOINTS macro
for recent Solaris.
This leads to two failures on current x86_64-pc-solaris-2.11
(none of x86_64-pc-linux)
that disappear if I undefined the macro.
Is it possible to commit this first or
should we first find a way to solve the problem?
I could add a single line diff that would remove
the macro definition in config/i386/nm-i386-sol2.h.
The other question after is what to do with the code
and comments related to CANNOT_STEP_HW_WATCHPOINTS macro
in infrun.c source.
Pierre Muller
Pascal language support maintainer for GDB
2010-04-23 Pierre Muller <muller@ics.u-strasbg.fr>
PR breakpoints/11531.
* testsuite/gdb.base/gdb11531.c: New file.
* testsuite/gdb.base/gdb11531.exp: New file.
Index: src/gdb/testsuite/gdb.base/gdb11531.c
===================================================================
RCS file: testsuite/gdb.base/gdb11531.c
diff -N testsuite/gdb.base/gdb11531.c
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ src/gdb/testsuite/gdb.base/gdb11531.c 23 Apr 2010 16:17:25 -0000
@@ -0,0 +1,40 @@
+/* This testcase is part of GDB, the GNU debugger.
+
+ Copyright 2010 Free Software Foundation, Inc.
+
+ Contributed by Pierre Muller.
+
+ 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 for Solaris specific watchpoint problem. */
+
+struct rec
+{
+ int x;
+ double y;
+ int z;
+};
+
+static struct rec myrec;
+
+int
+main ()
+{
+ myrec.x = 5;
+ myrec.y = 3.4;
+ myrec.z = 56;
+ myrec.x = 78;
+ return myrec.x;
+}
+
Index: src/gdb/testsuite/gdb.base/gdb11531.exp
===================================================================
RCS file: testsuite/gdb.base/gdb11531.exp
diff -N testsuite/gdb.base/gdb11531.exp
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ src/gdb/testsuite/gdb.base/gdb11531.exp 23 Apr 2010 16:17:25 -0000
@@ -0,0 +1,59 @@
+# This testcase is part of GDB, the GNU debugger.
+
+# Copyright 2010 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 GDB for Solaris specific watchpoint problem.
+
+if $tracelevel then {
+ strace $tracelevel
+}
+
+set prms_id 0
+set bug_id 0
+
+set testfile "gdb11531"
+
+if { [prepare_for_testing $testfile.exp $testfile $testfile.c {debug}] } {
+ return -1;
+}
+
+
+# Do not use run_to main
+# as this sets a breakpoint at main.
+# If the breakpoint is at the same instruction as the
+# watchpoint value assignment
+# you can fall into the problem of the stepping over the breakpoint
+# location that can also trigger a watchpoint miss
+# This is not the problem reported here.
+
+gdb_test "start" ".*Temporary breakpoint.*"
+
+gdb_test "watch myrec.x" ".*atchpoint \[0-9\]+: myrec\.x" "Set watchpoint "
+
+gdb_test "next" \
+ "Old value = 0.*New value = 5.*" \
+ "watchpoint variable triggers at next"
+
+gdb_test "continue" \
+ "Old value = .*New value = 78.*" \
+ "watchpoint variable triggers at continue"
+
+gdb_test "continue" ".*Program exited.*" "Continue to program exit"
+
+gdb_test "start" "" "restart"
+
+gdb_test "next" "Old value = 0.*New value = 5.*" "watchpoint triggers after
second start"
+
next reply other threads:[~2010-04-23 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 16:41 Pierre Muller [this message]
2010-04-23 17:29 ` Joel Brobecker
2010-04-23 18:16 ` Pedro Alves
2010-04-23 18:25 ` Joel Brobecker
2010-04-24 15:13 ` [RFA- v2] Testcase for bug report 11531 and fix for Solaris Pierre Muller
2010-04-25 13:20 ` Joel Brobecker
2010-04-26 11:24 ` [RFA- v3] " Pierre Muller
2010-04-26 16:49 ` Joel Brobecker
2010-04-26 20:50 ` Pierre Muller
2010-04-25 20:10 ` [RFA- v2] " Pedro Alves
2010-04-26 10:55 ` [RFA- v2] Remove CANNOT_STEP_HW_WATCHPOINTS related code (was fix for bug 11531) Pierre Muller
2010-04-26 11:26 ` Pedro Alves
2010-04-26 11:50 ` Pierre Muller
2010-04-26 11:56 ` Pedro Alves
2010-04-26 12:03 ` Pierre Muller
2010-04-26 11:29 ` Mark Kettenis
2010-04-26 11:52 ` Pierre Muller
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='000301cae303$d6d068b0$84713a10$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--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