e707fc445e
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.
58 lines
1.8 KiB
Plaintext
58 lines
1.8 KiB
Plaintext
# Copyright 2012-2018 Free Software Foundation, Inc.
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
load_lib mi-support.exp
|
|
set MIFLAGS "-i=mi"
|
|
|
|
gdb_exit
|
|
if [mi_gdb_start] {
|
|
continue
|
|
}
|
|
|
|
standard_testfile .c
|
|
set opts {debug}
|
|
|
|
if [build_executable $testfile.exp $testfile $srcfile $opts] {
|
|
return -1
|
|
}
|
|
|
|
mi_delete_breakpoints
|
|
mi_gdb_reinitialize_dir $srcdir/$subdir
|
|
mi_gdb_load ${binfile}
|
|
|
|
if ![mi_run_to_main] {
|
|
untested "could not run to main"
|
|
return -1
|
|
}
|
|
|
|
# Test creating a register-based variable. We pick
|
|
# register SP since it is a pointer to data. This checks
|
|
# for a regression when creating MI variables from pointers
|
|
# with "print object" enabled.
|
|
|
|
# Enable "print object"
|
|
mi_gdb_test "-gdb-set print object on" ".*"
|
|
|
|
# Test creating a variable for $sp.
|
|
# We use a explicit cast to (void *) as that is the
|
|
# type that caused the bug this testcase is testing for.
|
|
mi_gdb_test "-var-create sp1 * ((void*)\$sp)" \
|
|
"\\^done,name=\"sp1\",numchild=\"0\",value=\"$hex\",type=\"void \\*\",thread-id=\"$decimal\",has_more=\"0\"" \
|
|
"-var-create sp1 * \$sp"
|
|
mi_gdb_test "-var-create sp2 @ ((void*)\$sp)" \
|
|
"\\^done,name=\"sp2\",numchild=\"0\",value=\"$hex\",type=\"void \\*\",has_more=\"0\"" \
|
|
"-var-create sp2 @ \$sp"
|
|
gdb_exit
|