Go to file
Tom de Vries 8ba97c1904 [gdb/doc] Fix negative repeat count examining memory example
The documentation for the examining memory command x contains an example:
...
You can also specify a negative repeat count to examine memory backward from
the given address.  For example, 'x/-3uh 0x54320' prints three halfwords (h)
at 0x54314, 0x54328, and 0x5431c.
...

The 0x54328 looks like a typo, which was intended to be 0x54318.

But the series uses a 4-byte distance, while the halfword size used in the
command means a 2-byte distance, so the series should be:
...
0x5431a, 0x5431c, and 0x5431e.
...

Fix this by updating the addresses in the example accordingly.

Reported here ( https://sourceware.org/pipermail/gdb/2021-November/049784.html
).
2021-11-18 19:22:51 +01:00
bfd elf/x86: Issue an error on discarded output .plt section 2021-11-18 07:58:52 -08:00
binutils Pass DEBUGINFOD_CFLAGS when compiling dwarf.c 2021-11-18 18:48:24 +10:30
config
contrib
cpu
elfcpp arm: add armv9-a architecture to -march 2021-11-01 10:51:03 +00:00
etc
gas Add multibyte character warning option to the assembler. 2021-11-18 16:48:19 +00:00
gdb [gdb/doc] Fix negative repeat count examining memory example 2021-11-18 19:22:51 +01:00
gdbserver Remove config.cache in gdbserver's "distclean" 2021-11-16 09:13:24 -07:00
gdbsupport gdbsupport: make gdb_assert_not_reached accept a format string 2021-11-18 11:29:19 -05:00
gnulib
gold -Waddress fixes for gold testsuite 2021-11-15 13:26:17 +10:30
gprof configure: regenerate in all projects that use libtool.m4 2021-09-27 20:31:24 +01:00
include RISC-V: Add instructions and operand set for z[fdq]inx 2021-11-18 14:43:23 +08:00
intl Regenerate a couple of files 2021-11-15 12:20:12 +10:30
ld elf/x86: Issue an error on discarded output .plt section 2021-11-18 07:58:52 -08:00
libbacktrace sync libbacktrace from gcc 2021-11-14 18:07:50 +10:30
libctf doc/ctf-spec.texi: Remove "@validatemenus off" 2021-11-09 05:35:42 -08:00
libdecnumber
libiberty
opcodes Re: Don't compile some opcodes files when bfd is 32-bit only 2021-11-18 18:55:16 +10:30
readline
sim sim: testsuite: add support for $pwd replacements 2021-11-16 20:21:59 -05:00
texinfo
zlib configure: regenerate in all projects that use libtool.m4 2021-09-27 20:31:24 +01:00
.cvsignore
.gitattributes
.gitignore
ar-lib
ChangeLog Document "memory-tag-violations". 2021-10-29 13:31:37 +03:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure top-level configure: setup target_configdirs based on repository 2021-09-28 12:21:21 +01:00
configure.ac top-level configure: setup target_configdirs based on repository 2021-09-28 12:21:21 +01:00
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 Import Makefile.def from gcc 2021-11-12 19:02:12 +10:30
Makefile.in Sync Makefile.tpl with GCC 2021-11-13 09:04:03 -08:00
Makefile.tpl Sync Makefile.tpl with GCC 2021-11-13 09:04:03 -08:00
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
multilib.am
README
README-maintainer-mode
setup.com
src-release.sh src-release.sh: add libbacktrace to GDB_SUPPORT_DIRS 2021-09-28 12:21:21 +01: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.