Go to file
Tom de Vries c82f680a94 [gdb/testsuite] Reimplement gdb.gdb/python-interrupts.exp as unittest
The test-case gdb.gdb/python-interrupts.exp:
- runs to captured_command_loop
- sets a breakpoint at set_active_ext_lang
- calls a python command
- verifies the command triggers the breakpoint
- sends a signal and verifies the result

The test-case is fragile, because (f.i. with -flto) it cannot be guaranteed
that captured_command_loop and set_active_ext_lang are available for setting
breakpoints.

Reimplement the test-case as unittest, using:
- execute_command_to_string to capture the output
- try/catch to catch the "Error while executing Python code" exception
- a new hook selftests::hook_set_active_ext_lang to raise the signal

Tested on x86_64-linux.
2021-10-19 23:50:50 +02:00
bfd Fix a potential illegal memory access when testing for a special LTO symbol name. 2021-10-19 16:02:49 +01:00
binutils Fix a potential illegal memory access when testing for a special LTO symbol name. 2021-10-19 16:02:49 +01:00
config
contrib
cpu
elfcpp
etc
gas Re: s12z/disassembler: call memory_error_func when appropriate 2021-10-14 13:08:46 +10:30
gdb [gdb/testsuite] Reimplement gdb.gdb/python-interrupts.exp as unittest 2021-10-19 23:50:50 +02:00
gdbserver [gdb/build] Add CXX_DIALECT to CXX 2021-10-04 18:51:09 +02:00
gdbsupport Fix format_pieces selftest on Windows 2021-10-19 13:14:48 -06:00
gnulib
gold [GOLD] Re: PowerPC64: Don't pretend to support multi-toc 2021-10-14 20:02:32 +10:30
gprof
include RISC-V: Add support for Zbs instructions 2021-10-07 17:09:25 +08:00
intl
ld ld: Adjust pr28158.rd for glibc 2.34 2021-10-16 08:12:25 -07:00
libbacktrace
libctf
libdecnumber
libiberty
opcodes z80/disassembler: call memory_error_func when appropriate 2021-10-11 14:07:03 +01:00
readline
sim sim: add --info-target for listing supported BFD targets 2021-10-04 02:19:58 -04: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
Makefile.in
Makefile.tpl
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.