Lines Matching full:we
4 * Since using watchpoints can be very slow, we have to take some pains to
5 * ensure that we don't run too long with them enabled or we run the risk
6 * of having the test timeout. To help avoid this, we insert some marker
7 * functions in the execution stream so we can set breakpoints at known
9 * this file. We use null bodied functions are markers since gdb does
12 * One place we need is a marker for when we start executing our tests
13 * instructions rather than any process startup code, so we insert one
14 * right after entering main(). Another is right before we finish, before
15 * we start executing any process termination code.
17 * Another problem we have to guard against, at least for the test
18 * suite, is that we need to ensure that the line that causes the
22 * the same line or part of the next line. Thus we ensure that there
101 /* The point of this is that we will set a breakpoint at this call. in func1()
104 instruction (true on a sun3 if this is gcc-compiled--FIXME we in func1()
106 future), then we will end up branching to the location just after in func1()
107 the breakpoint. And we better not confuse that with hitting the in func1()
141 /* We have a watchpoint on ptr1->val. It should be triggered if in main()
145 /* This should not trigger the watchpoint. If it does, then we in main()
146 used the wrong value chain to re-insert the watchpoints or we in main()
151 /* We have a watchpoint on ptr1->val. It should be triggered if in main()
155 /* This should not trigger the watchpoint. If it does, then we in main()
156 used the wrong value chain to re-insert the watchpoints or we in main()
161 /* We're going to watch locals of func2, to see that out-of-scope in main()