Go to file
Simon Marchi 850ed749b4 gdb: add logging to dwarf2_initialize_objfile
I added these printouts while working on 27541.  I won't have a fix for
that right now, but I thought that it would be useful to merge them
upstream, as they help understand what happens in that function.

gdb/ChangeLog:

	* dwarf2/read.c (dwarf2_initialize_objfile): Add debug prints.

Change-Id: I790c0d53383327038cb5dd705f74c8c978e0a7ec
2021-03-15 13:24:02 -04:00
bfd Automatic date update in version.in 2021-03-15 00:00:06 +00:00
binutils Add a symbols-only mode to nm. 2021-03-15 10:55:49 +00:00
config
contrib
cpu
elfcpp
etc
gas aarch64: Add few missing system registers 2021-03-12 14:20:46 +00:00
gdb gdb: add logging to dwarf2_initialize_objfile 2021-03-15 13:24:02 -04:00
gdbserver
gdbsupport
gnulib
gold
gprof
include Add values for NetBSD .note.netbsd.ident notes (PaX). 2021-03-12 14:37:51 +00:00
intl
ld ld: don't chance overrunning PE .reloc section content 2021-03-15 11:00:44 +01:00
libctf
libdecnumber
libiberty
opcodes aarch64: Add few missing system registers 2021-03-12 14:20:46 +00:00
readline
sim sim: rename BUILD_LDFLAGS to LDFLAGS_FOR_BUILD 2021-03-13 11:21:13 -05:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog sim: drop dep on configure-gdb 2021-03-12 19:50:26 -05: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 sim: drop dep on configure-gdb 2021-03-12 19:50:26 -05:00
Makefile.in sim: drop dep on configure-gdb 2021-03-12 19:50:26 -05:00
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.