Go to file
Pedro Alves 4898949800 Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver
This implements support for the new GDB_THREAD_OPTION_EXIT thread
option for Linux GDBserver.

Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Change-Id: I96b719fdf7fee94709e98bb3a90751d8134f3a38
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27338
2023-11-13 14:16:10 +00:00
bfd Automatic date update in version.in 2023-11-13 00:00:07 +00:00
binutils bfd, binutils: add gfx11 amdgpu architectures 2023-11-10 13:20:22 -05:00
config config/debuginfod.m4: Add check for libdebuginfod 0.188 2023-09-27 15:11:13 -04:00
contrib
cpu
elfcpp MIPS: Change all E_MIPS_* to EF_MIPS_* 2023-11-10 14:03:17 +00:00
etc
gas GAS/MIPS: Fix testcase module-defer-warn2 for r2+ triples 2023-11-10 16:00:06 +00:00
gdb Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit 2023-11-13 14:16:10 +00:00
gdbserver Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver 2023-11-13 14:16:10 +00:00
gdbsupport Remove EXTERN_C and related defines 2023-11-06 20:31:12 -07:00
gnulib
gold Gold/MIPS: Use EM_MIPS instead of EM_MIPS_RS3_LE for little endian 2023-11-10 16:28:42 +00:00
gprof
gprofng gprofng: remove dependency on help2man 2023-11-01 19:25:06 -07:00
include bfd, binutils: add gfx11 amdgpu architectures 2023-11-10 13:20:22 -05:00
intl
ld Add ability to change linker warning messages into errors when reporting executable stacks and/or executable segments. 2023-11-10 11:37:27 +00:00
libbacktrace
libctf libctf: fix creation-time parent/child dict confusions 2023-10-20 18:09:54 +01:00
libdecnumber
libiberty
libsframe
opcodes Add support for ilp32 register alias. 2023-11-10 14:45:09 +08:00
readline
sim sim/riscv: fix JALR instruction simulation 2023-10-18 17:55:31 +01:00
texinfo
zlib
.cvsignore
.editorconfig
.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 sim: add distclean dep for gnulib 2023-10-15 23:00:33 +05:45
Makefile.in sim: add distclean dep for gnulib 2023-10-15 23:00:33 +05:45
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.