Go to file
Andrew Burgess e707fc445e gdb: Don't store a thread-id for floating varobj
When creating a varobj with -var-create a user can create either fixed
varobj, or floating varobj.

A fixed varobj will always be evaluated within the thread/frame/block in
which the varobj was created, if that thread/frame/block is no longer
available then the varobj is considered out of scope.

A floating varobj will always be evaluated within the current
thread/frame/block.

Despite never using them GDB was storing the thread/frame/block into a
floating varobj, and the thread-id would then be displayed when GDB
reported on the state of the varobj, this could confuse a user into
thinking that the thread-id was relevant.

This commit prevents GDB storing the thread/frame/block onto floating
varobj, and updates the few tests where this impacts the results.

gdb/ChangeLog:

	* varobj.c (varobj_create): Don't set valid_block when creating a
	floating varobj.

gdb/testsuite/ChangeLog:

	* gdb.python/py-mi.exp: Don't expect a thread-id for floating
	varobj.
	* gdb.mi/mi-var-create-rtti.exp: Likewise.
2018-01-21 15:47:28 +00:00
bfd Automatic date update in version.in 2018-01-21 00:00:35 +00:00
binutils Update Bulgarian translation of the binutils sub-directory 2018-01-18 09:38:59 +00:00
config
cpu Add note about 2.30 branch creation to changelogs 2018-01-13 13:26:38 +00:00
elfcpp Add note about 2.30 branch creation to changelogs 2018-01-13 13:26:38 +00:00
etc
gas [gas/ARM] Remove spurious comments 2018-01-19 14:17:24 +00:00
gdb gdb: Don't store a thread-id for floating varobj 2018-01-21 15:47:28 +00:00
gold PowerPC PLT stub alignment fixes 2018-01-18 22:25:21 +10:30
gprof Update pot files 2018-01-13 13:56:48 +00:00
include Add note about 2.30 branch creation to changelogs 2018-01-13 13:26:38 +00:00
intl
ld x86: Check the versioned __tls_get_addr symbol 2018-01-20 14:29:36 -08:00
libdecnumber
libiberty
opcodes RISC-V: Fix bug in prior addi/c.nop patch. 2018-01-17 14:04:16 -08:00
readline
sim
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog Update notes on how to make a release 2018-01-13 14:29:27 +00: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
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release.sh Update notes on how to make a release 2018-01-13 14:29:27 +00: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.