]>
git.ipfire.org Git - thirdparty/binutils-gdb.git/blob - gdb/testsuite/gdb.reverse/watch-reverse.c
1 /* This testcase is part of GDB, the GNU debugger.
3 Copyright 2008-2012 Free Software Foundation, Inc.
5 This program is free software; you can redistribute it and/or modify
6 it under the terms of the GNU General Public License as published by
7 the Free Software Foundation; either version 3 of the License, or
8 (at your option) any later version.
10 This program is distributed in the hope that it will be useful,
11 but WITHOUT ANY WARRANTY; without even the implied warranty of
12 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
13 GNU General Public License for more details.
15 You should have received a copy of the GNU General Public License
16 along with this program. If not, see <http://www.gnu.org/licenses/>. */
21 * Since using watchpoints can be very slow, we have to take some pains to
22 * ensure that we don't run too long with them enabled or we run the risk
23 * of having the test timeout. To help avoid this, we insert some marker
24 * functions in the execution stream so we can set breakpoints at known
25 * locations, without worrying about invalidating line numbers by changing
26 * this file. We use null bodied functions are markers since gdb does
27 * not support breakpoints at labeled text points at this time.
29 * One place we need is a marker for when we start executing our tests
30 * instructions rather than any process startup code, so we insert one
31 * right after entering main(). Another is right before we finish, before
32 * we start executing any process termination code.
34 * Another problem we have to guard against, at least for the test
35 * suite, is that we need to ensure that the line that causes the
36 * watchpoint to be hit is still the current line when gdb notices
37 * the hit. Depending upon the specific code generated by the compiler,
38 * the instruction after the one that triggers the hit may be part of
39 * the same line or part of the next line. Thus we ensure that there
40 * are always some instructions to execute on the same line after the
41 * code that should trigger the hit.
55 struct foo struct1
, struct2
, *ptr1
, *ptr2
;
84 void recurser (x
) int x
;
112 x
= 1; /* second x assignment */
120 /* The point of this is that we will set a breakpoint at this call.
122 Then, if DECR_PC_AFTER_BREAK equals the size of a function call
123 instruction (true on a sun3 if this is gcc-compiled--FIXME we
124 should use asm() to make it work for any compiler, present or
125 future), then we will end up branching to the location just after
126 the breakpoint. And we better not confuse that with hitting the
148 for (count
= 0; count
< 4; count
++) {
150 ival3
= count
; ival4
= count
;
152 ival1
= count
; /* Outside loop */
154 ival3
= count
; ival4
= count
;
158 static char msg
[] = "type stuff for buf now:";
159 write (1, msg
, sizeof (msg
) - 1);
160 read (0, &buf
[0], 5);
164 /* We have a watchpoint on ptr1->val. It should be triggered if
165 ptr1's value changes. */
168 /* This should not trigger the watchpoint. If it does, then we
169 used the wrong value chain to re-insert the watchpoints or we
170 are not evaluating the watchpoint expression correctly. */
174 /* We have a watchpoint on ptr1->val. It should be triggered if
175 ptr1's value changes. */
178 /* This should not trigger the watchpoint. If it does, then we
179 used the wrong value chain to re-insert the watchpoints or we
180 are not evaluating the watchpoint expression correctly. */
184 /* We're going to watch locals of func2, to see that out-of-scope
185 watchpoints are detected and properly deleted.
189 /* This invocation is used for watches of a single
193 /* This invocation is used for watches of an expression
194 involving a local variable. */
197 /* This invocation is used for watches of a static
198 (non-stack-based) local variable. */
201 /* This invocation is used for watches of a local variable
202 when recursion happens.