Go to file
Guinevere Larsen c8cfd51787 gdb/testsuite: fix gdb.python/py-framefilter-invalidarg.exp with clang
The final test of gdb.python/py-framefilter-invalidarg.exp expected that
the the backtrace only printed the source file name. However, when using
clang, gdb will always print the full path to the file, which would
cause the test to fail. This commit introduces a regexp that optionally
matches paths, preprended to the file name, which fixes the clang
failure without introducing gcc failures.

Approved-By: Andrew Burgess <aburgess@redhat.com>
2024-08-02 09:06:26 -03:00
bfd Automatic date update in version.in 2024-08-02 00:00:31 +00:00
binutils skip_attr_bytes assertion (data) <= (end) fail 2024-08-01 21:52:34 +09:30
config
contrib
cpu Add markers for 2.43 branch/release 2024-07-20 12:43:19 +01:00
elfcpp Add markers for 2.43 branch/release 2024-07-20 12:43:19 +01:00
etc
gas gas: drop unnecessary use of tc_comment_chars 2024-08-02 09:44:53 +02:00
gdb gdb/testsuite: fix gdb.python/py-framefilter-invalidarg.exp with clang 2024-08-02 09:06:26 -03:00
gdbserver gdb: AArch64: Support MTE on baremetal 2024-08-01 10:01:39 +01:00
gdbsupport
gnulib
gold PR32032 dwp segfaults on hello world binary 2024-07-29 16:25:59 +09:30
gprof Change version to 2.43.50 2024-07-20 13:16:33 +01:00
gprofng gprofng: 32018 Compilation of binutils 2.43 failed on CentOS 6 2024-07-30 12:06:26 -07:00
include libctf, include: add ctf_dict_set_flag: less enum dup checking by default 2024-07-31 21:02:05 +01:00
ld LoongArch: Fix ld FAIL test cases 2024-08-01 10:23:37 +08:00
libbacktrace
libctf libctf: fix ctf_archive_count return value on big-endian 2024-07-31 21:10:06 +01:00
libdecnumber
libiberty
libsframe
opcodes Updated translations for the bfd, binutils, gas, ld and opcodes directories 2024-07-29 11:57:25 +01:00
readline
sim
texinfo
zlib
.cvsignore
.editorconfig
.gitattributes
.gitignore
.pre-commit-config.yaml
ar-lib
ChangeLog Add markers for 2.43 branch/release 2024-07-20 12:43:19 +01:00
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
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
SECURITY.txt
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.