[PATCH 0/4] gdb, btrace: infrun fixes

[Pedro Alves]

Hi Markus,

I ran the tests included in the series against pristine / unfixed GDB, and got:

	Using /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file.
	Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/stepn.exp ...
	Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/implicit-stop-replaying.exp ...
	FAIL: gdb.btrace/implicit-stop-replaying.exp: thread apply 1 info record
	Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/step-hang.exp ...
	FAIL: gdb.btrace/step-hang.exp: continue until exit (timeout)
	Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/cont-hang.exp ...
	FAIL: gdb.btrace/cont-hang.exp: continue until exit (timeout)
	Running /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/multi-thread-break-hang.exp ...
	FAIL: gdb.btrace/multi-thread-break-hang.exp: stepi.2 (timeout)
	FAIL: gdb.btrace/multi-thread-break-hang.exp: stepi.3 (timeout)

The curious thing is that stepn.exp doesn't fail, it passes anyhow.  Is that expected?

Also, I diffed gdb.log before/after patch, and noticed a difference.  GDB no longer prints the current
location:

   No more reverse-execution history.
  -main () at /home/pedro/gdb/binutils-gdb/src/gdb/testsuite/gdb.btrace/record_goto.c:50
   50       return 0;     /* main.3 */

Is this expected?

Thanks,
Pedro Alves