Re: [patch] circ.exp

["Abid, Hafiz" <hafiz_abid at mentor dot com>]

> > 4) Many tests were expecting current stack frame to be printed as  
> result of
> > tfind command e.g. "#0  func9 .*".  But this only happens when  
> traceframe_number
> > is -1.  In the following code, old_frame_id equal to current frame  
> id unless
> > traceframe_number < 0.
> >
>
> I'm confused.  Does the tfind in question switch to a different
> frame or not?
I have observed that location is only printed first time we give tfind  
command (or give it after doing a tfind none).
If you see the example session below, you will see that 'tfind start'  
prints the following line.
#0  func0 () at ../.././../git/gdb/testsuite/gdb.trace/circ.c:28

But next tfind does not print any such line. The test was assuming the  
presence of this line every time. I am not sure what is expected  
behavior is though.

(gdb) tstart
(gdb) info tracepoints
Num     Type           Disp Enb Address    What
1       tracepoint     keep y   0x080483b7 in func0
                                           at  
../.././../git/gdb/testsuite/gdb.trace/circ.c:28
        collect testload
	installed on target
2       tracepoint     keep y   0x080483bc in func1
                                           at  
../.././../git/gdb/testsuite/gdb.trace/circ.c:32
        collect testload
	installed on target
(gdb) c
Continuing.

Breakpoint 3, end () at ../.././../git/gdb/testsuite/gdb.trace/circ.c:72
72	}
(gdb) tstop
(gdb) tfind start
Found trace frame 0, tracepoint 1
#0  func0 () at ../.././../git/gdb/testsuite/gdb.trace/circ.c:28
28	}
(gdb) tfind
Found trace frame 1, tracepoint 2
32	}
(gdb)


Regards,
Abid