Go to file
Simon Marchi e19f824829 Revert (part of) "gdb fix for catch-syscall.exp"
This reverts (par of) commit ab19827912.
This commit changed what the test expects when catching the execve
syscall based on the behavior seen on a Linux PowerPC machine.  That is,
we get an "entry" event, but no "return" event.  This is not what we get
on Linux with other architectures, though, and it seems like a
PowerPC-specific bug.

Revert the part of the patch related to this, but not the other hunk.

Change-Id: I4248776e4299f10999487be96d4acd1b33639996
2021-11-24 14:34:36 -05:00
bfd Automatic date update in version.in 2021-11-24 00:00:08 +00:00
binutils Fix an illegal memory access parsing a corrupt sysroff file. 2021-11-24 17:02:02 +00:00
config
contrib
cpu
elfcpp
etc
gas Update bug reporting address 2021-11-23 15:39:26 +10:30
gdb Revert (part of) "gdb fix for catch-syscall.exp" 2021-11-24 14:34:36 -05:00
gdbserver gdb: pass more const target_waitstatus by reference 2021-11-22 13:57:54 -05:00
gdbsupport gdb: introduce target_waitkind_str, use it in target_waitstatus::to_string 2021-11-22 13:57:49 -05:00
gnulib
gold Update bug reporting address 2021-11-23 15:39:26 +10:30
gprof Update bug reporting address 2021-11-23 15:39:26 +10:30
include AArch64: Add support for AArch64 EFI (efi-*-aarch64). 2021-11-23 09:36:39 +00:00
intl Regenerate a couple of files 2021-11-15 12:20:12 +10:30
ld Update bug reporting address 2021-11-23 15:39:26 +10:30
libbacktrace sync libbacktrace from gcc 2021-11-14 18:07:50 +10:30
libctf doc/ctf-spec.texi: Remove "@validatemenus off" 2021-11-09 05:35:42 -08:00
libdecnumber
libiberty
opcodes Update bug reporting address 2021-11-23 15:39:26 +10:30
readline
sim sim: v850: fix cpu_option testsuite handling 2021-11-20 23:13:50 -05:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def Import Makefile.def from gcc 2021-11-12 19:02:12 +10:30
Makefile.in Sync Makefile.tpl with GCC 2021-11-13 09:04:03 -08:00
Makefile.tpl Sync Makefile.tpl with GCC 2021-11-13 09:04:03 -08:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
test-driver
ylwrap

		   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.