Go to file
Andrew Burgess c14993e9dc gdb/corefile: write NT_GDB_TDESC based on signalled thread
When creating a core file from within GDB we include a NT_GDB_TDESC
that includes the target description of the architecture in use.

For architectures with dynamic architectures (e.g. AArch64 with
sve/sme) the original architecture, calculated from the original
target description, might not match the per-thread architecture.

In the general case, where each thread has a different architecture,
then we really need a separate NT_GDB_TDESC for each thread, however,
there's currently no way to read in multiple NT_GDB_TDESC.

This commit is a step towards per-thread NT_GDB_TDESC.  In this commit
I have updated the function that writes the NT_GDB_TDESC to accept a
gdbarch (rather than calling target_gdbarch() to find a gdbarch), and
I now pass in the gdbarch of the signalled thread.

In many cases (though NOT all) targets with dynamic architectures
really only use a single architecture, even when there are multiple
threads, so in the common case, this should ensure that GDB emits an
architecture that is more likely to be correct.

Additional work will be needed in order to support corefiles with
truly per-thread architectures, but that will need to be done in the
future.
2023-10-03 17:43:50 +01:00
bfd Automatic date update in version.in 2023-10-03 00:00:46 +00:00
binutils MIPS: Fix `readelf -S bintest' test for n64 targets 2023-10-03 12:41:02 +01:00
config config/debuginfod.m4: Add check for libdebuginfod 0.188 2023-09-27 15:11:13 -04:00
contrib
cpu
elfcpp
etc
gas Fix memory leak in RiscV assembler. 2023-10-02 16:23:14 +01:00
gdb gdb/corefile: write NT_GDB_TDESC based on signalled thread 2023-10-03 17:43:50 +01:00
gdbserver Remove explanatory comments from includes 2023-09-20 11:45:16 -06:00
gdbsupport Remove explanatory comments from includes 2023-09-20 11:45:16 -06:00
gnulib
gold gold: Use char16_t, char32_t instead of uint16_t, uint32_t as character types 2023-09-06 17:20:20 -07:00
gprof
gprofng gprofng: 30834 improve disassembly output for call and branch instructions 2023-09-21 18:56:30 -07:00
include x86-64: Add -z mark-plt and -z nomark-plt 2023-09-29 07:58:53 -07:00
intl
ld Use bfd_get_current_time in places where it is suitable 2023-10-02 13:24:05 +01:00
libbacktrace
libctf
libdecnumber
libiberty
libsframe
opcodes opcodes: microblaze: Add wdc.ext.clear and wdc.ext.flush insns 2023-09-27 14:47:01 +01:00
readline
sim
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
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 src-release.sh (SIM_SUPPORT_DIRS): Add libsframe, libctf/swap.h and gnulib 2023-09-06 04:15:23 +02:00
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.