No description
Find a file
Gary Benson 5ee44bfa6b Remove code to cope with LWPs wrapped as PIDs
Historically the Linux x86 watchpoint code did not cope with multi-
threaded processes and LWP IDs were passed to it wrapped as PIDs.
Not all entry points were converted when the Linux x86 watchpoint
code was made multi-thread-aware, so a handler was left in place to
cope with wrapped LWPs.  Since then all such entry points have been
converted to pass regular LWPs and the handler is now redundant.
This commit removes the handler and adds assertions to ensure no
wrapped LWPs are passed in future.

gdb/ChangeLog:

	* x86-linux-nat.c (x86_linux_dr_get, x86_linux_dr_set):
	Remove code to cope with LWPs wrapped as PIDs.
	Add assertions to ensure no wrapped LWPs are passed.
2014-09-04 15:23:21 +01:00
bfd daily update 2014-09-04 09:30:40 +09:30
binutils aarch64: Decode dwarf2 register numbers 2014-08-22 14:40:10 -07:00
config Fix --diable-shared --enable-plugins build breakage 2014-08-19 21:59:56 +09:30
cpu
elfcpp Make Elf_file::section_name() a const function, so that it can be used in 2014-09-02 15:44:58 -07:00
etc
gas MIPS: Update the list of addr32 targets 2014-09-04 09:46:01 +01:00
gdb Remove code to cope with LWPs wrapped as PIDs 2014-09-04 15:23:21 +01:00
gold Add NaCl (NativeClient) specific classes Target_mips_nacl and 2014-09-03 09:44:11 -07:00
gprof Fix --diable-shared --enable-plugins build breakage 2014-08-19 21:59:56 +09:30
include [PATCH/AArch64] Implement LSE feature 2014-09-03 14:53:53 +01:00
intl
ld Fix testsuite ld_simple_link_defsyms for windows targets 2014-08-29 10:34:18 +09:30
libdecnumber
libiberty
opcodes [PATCH/AArch64] Generic support for all system registers using mrs and msr 2014-09-03 14:53:53 +01:00
readline
sim Shadow SIM's debug_printf function 2014-08-28 11:59:09 +01:00
texinfo
.cvsignore
.gitattributes
.gitignore
ChangeLog src-release.sh: Convert src-release to a shell script 2014-08-27 13:50:06 +01:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure
configure.ac
COPYING
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
COPYING3
COPYING3.LIB
depcomp
djunpack.bat
install-sh
libtool.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
lt~obsolete.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release.sh src-release.sh: Convert src-release to a shell script 2014-08-27 13:50:06 +01:00
symlink-tree
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.