Check tracefile is generated by binary execution
authorYao Qi <yao@codesourcery.com>
Fri, 21 Mar 2014 04:52:24 +0000 (12:52 +0800)
committerYao Qi <yao@codesourcery.com>
Tue, 22 Apr 2014 01:57:44 +0000 (09:57 +0800)
commitb4429ea262cfbeb9a6ebd9308654b0883b19d1a5
tree338b1e05c454303dcf3d21e023591905eab0903b
parent48b6e87ef297136a6409c2c993c4626f28bbb4d1
Check tracefile is generated by binary execution

In gdb.trace/tfile.exp, we execute binary to generate tracefile,

  remote_exec target "$binfile"

however, this fails on bare metal target.  This patch is to
handle binary execution failure by running binary in GDB.
The binary will do some io operation to generate tracefile, so
we need a check 'target_info exists gdb,nofileio'.

This patch is to check whether tracefile is generated.  tfile.exp can
be skipped if generation is failed, while test_tfind_tfile in
mi-traceframe-changed.exp is skipped if generated failed.  The rest of
the mi-traceframe-changed.exp can still be executed, because on some
bare metal targets, the remote stub supports tracepoint but doesn't
support fileio.

gdb/testsuite:

2014-04-22  Yao Qi  <yao@codesourcery.com>

* lib/trace-support.exp (generate_tracefile): New procedure.
* gdb.trace/tfile.exp: Skip the test if generate_tracefile
return 0.
* gdb.trace/mi-traceframe-changed.exp: Invoke test_tfind_tfile
if generate_tracefile returns 1.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.trace/mi-traceframe-changed.exp
gdb/testsuite/gdb.trace/tfile.exp
gdb/testsuite/lib/trace-support.exp
This page took 0.034424 seconds and 4 git commands to generate.