Binutils with MCST patches
Go to file
Yao Qi b4429ea262 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.
2014-04-22 09:57:44 +08:00
bfd daily update 2014-04-22 09:30:39 +09:30
binutils mach-o: layout executables 2014-04-18 14:32:43 +02:00
config
cpu
elfcpp 2014-04-15 Sasa Stankovic <Sasa.Stankovic@imgtec.com> 2014-04-15 12:09:44 -07:00
etc
gas Fix more fallout from TC_CONS_FIX_NEW change 2014-04-16 23:00:29 +09:30
gdb Check tracefile is generated by binary execution 2014-04-22 09:57:44 +08:00
gold Allow target to decide whether to include a section. 2014-04-15 11:56:18 -07:00
gprof
include Mach-O: Add objdump -P dyld_info to dump dyld data. 2014-04-16 12:16:02 +02:00
intl
ld Fix alpha-elf relaxation 2014-04-21 08:14:18 -07:00
libdecnumber
libiberty
opcodes Add support for Intel SGX instructions 2014-04-04 08:24:47 -07:00
readline
sim Add support for two new moxie sign-extension instructions 2014-04-02 23:58:01 -04:00
texinfo
.cvsignore
.gitignore
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
ChangeLog This fixes PR bootstrap/60620: 2014-04-04 22:54:42 +02:00
MAINTAINERS
Makefile.def This fixes PR bootstrap/60620: 2014-04-04 22:54:42 +02:00
Makefile.in This fixes PR bootstrap/60620: 2014-04-04 22:54:42 +02:00
Makefile.tpl
README
README-maintainer-mode
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
depcomp
djunpack.bat
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
setup.com
src-release
symlink-tree
ylwrap

README

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.

If you are receiving this as part of a GDB release, see the file gdb/README.
If with a binutils release, see binutils/README;  if with a libg++ release,
see libg++/README, etc.  That'll give you info about this
package -- supported targets, how to use it, how to report bugs, etc.

It is now possible to automatically configure and build a variety of
tools with one command.  To build all of the tools contained herein,
run the ``configure'' script here, e.g.:

	./configure 
	make

To install them (by default in /usr/local/bin, /usr/local/lib, etc),
then do:
	make install

(If the configure script can't determine your type of computer, give it
the name as an argument, for instance ``./configure sun4''.  You can
use the script ``config.sub'' to test whether a name is recognized; if
it is, config.sub translates it to a triplet specifying CPU, vendor,
and OS.)

If you have more than one compiler on your system, it is often best to
explicitly set CC in the environment before running configure, and to
also set CC when running make.  For example (assuming sh/bash/ksh):

	CC=gcc ./configure
	make

A similar example using csh:

	setenv CC gcc
	./configure
	make

Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.