2018-01-01 05:43:02 +01:00
|
|
|
# Copyright 1998-2018 Free Software Foundation, Inc.
|
1999-04-16 03:35:26 +02:00
|
|
|
#
|
|
|
|
# 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
|
2007-08-23 20:14:19 +02:00
|
|
|
# the Free Software Foundation; either version 3 of the License, or
|
1999-04-16 03:35:26 +02:00
|
|
|
# (at your option) any later version.
|
2007-08-23 20:14:19 +02:00
|
|
|
#
|
1999-04-16 03:35:26 +02:00
|
|
|
# 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.
|
2007-08-23 20:14:19 +02:00
|
|
|
#
|
1999-04-16 03:35:26 +02:00
|
|
|
# You should have received a copy of the GNU General Public License
|
2007-08-23 20:14:19 +02:00
|
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
1999-04-16 03:35:26 +02:00
|
|
|
#
|
|
|
|
# This file was written by Kendra.
|
|
|
|
|
|
|
|
#
|
|
|
|
# Test debugging assembly level programs.
|
|
|
|
# This file uses asmsrc[12].s for input.
|
|
|
|
#
|
|
|
|
|
|
|
|
|
2000-07-04 04:47:08 +02:00
|
|
|
set asm-arch ""
|
2003-11-29 14:55:17 +01:00
|
|
|
set asm-note "empty"
|
2000-07-04 04:47:08 +02:00
|
|
|
set asm-flags ""
|
2005-10-31 21:33:22 +01:00
|
|
|
set link-flags "-e _start"
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags ""
|
2000-07-04 04:47:08 +02:00
|
|
|
|
2012-06-25 22:11:43 +02:00
|
|
|
set obj_include -I[standard_output_file {}]
|
|
|
|
|
2003-05-07 23:51:06 +02:00
|
|
|
switch -glob -- [istarget] {
|
2003-05-30 04:51:46 +02:00
|
|
|
"alpha*-*-*" {
|
|
|
|
set asm-arch alpha
|
|
|
|
# ??? Won't work with ecoff systems like Tru64, but then we also
|
|
|
|
# don't have any other -g flag that creates mdebug output.
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-no-mdebug -I${srcdir}/${subdir} $obj_include"
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gdwarf-2"
|
2003-05-30 04:51:46 +02:00
|
|
|
}
|
2011-01-19 21:26:10 +01:00
|
|
|
"arm*-*-*" {
|
2003-05-07 23:51:06 +02:00
|
|
|
set asm-arch arm
|
|
|
|
}
|
2015-09-16 16:13:29 +02:00
|
|
|
"aarch64*-*-*" {
|
|
|
|
set asm-arch aarch64
|
|
|
|
}
|
2011-07-06 20:40:30 +02:00
|
|
|
"bfin-*-*" {
|
|
|
|
set asm-arch bfin
|
|
|
|
}
|
2003-12-13 02:01:08 +01:00
|
|
|
"frv-*-*" {
|
|
|
|
set asm-arch frv
|
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
"s390-*-*" {
|
|
|
|
set asm-arch s390
|
|
|
|
}
|
2003-05-07 23:52:53 +02:00
|
|
|
"s390x-*-*" {
|
|
|
|
set asm-arch s390x
|
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
"x86_64-*-*" {
|
|
|
|
set asm-arch x86_64
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gdwarf-2"
|
2003-05-07 23:51:06 +02:00
|
|
|
}
|
|
|
|
"i\[3456\]86-*-*" {
|
|
|
|
set asm-arch i386
|
|
|
|
}
|
2009-05-18 15:25:35 +02:00
|
|
|
"lm32-*" {
|
|
|
|
set asm-arch lm32
|
|
|
|
}
|
2004-10-05 06:13:42 +02:00
|
|
|
"m32r*-linux*" {
|
|
|
|
set asm-arch m32r-linux
|
|
|
|
}
|
2006-04-21 01:24:23 +02:00
|
|
|
"m32c-*-*" {
|
|
|
|
set asm-arch m32c
|
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
"m32r*-*" {
|
|
|
|
set asm-arch m32r
|
2004-01-30 22:23:46 +01:00
|
|
|
append link-flags "--whole-archive -lgloss --no-whole-archive"
|
2003-05-07 23:51:06 +02:00
|
|
|
}
|
|
|
|
"m6811-*-*" {
|
|
|
|
set asm-arch m68hc11
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-mshort-double -m68hc11 --no-warn -I${srcdir}/${subdir} $obj_include"
|
2005-11-11 12:18:53 +01:00
|
|
|
set debug-flags "-gdwarf-2"
|
|
|
|
# This asm test is specific and uses the linker directly.
|
|
|
|
# We must not use the target board linker script defined for other
|
|
|
|
# tests. Remove it and restore it later on.
|
|
|
|
set board [target_info name]
|
|
|
|
set old_ldscript [board_info $board ldscript]
|
|
|
|
unset_board_info "ldscript"
|
2003-05-07 23:51:06 +02:00
|
|
|
}
|
|
|
|
"m6812-*-*" {
|
|
|
|
set asm-arch m68hc11
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-mshort-double -m68hc12 --no-warn -I${srcdir}/${subdir} $obj_include"
|
2005-11-11 12:18:53 +01:00
|
|
|
set debug-flags "-gdwarf-2"
|
|
|
|
# This asm test is specific and uses the linker directly.
|
|
|
|
# We must not use the target board linker script defined for other
|
|
|
|
# tests. Remove it and restore it later on.
|
|
|
|
set board [target_info name]
|
|
|
|
set old_ldscript [board_info $board ldscript]
|
|
|
|
set_board_info ldscript ""
|
2003-05-07 23:51:06 +02:00
|
|
|
}
|
|
|
|
"mips*-*" {
|
|
|
|
set asm-arch mips
|
|
|
|
}
|
2014-03-25 15:39:32 +01:00
|
|
|
"powerpc64le-*" {
|
|
|
|
set asm-arch powerpc64le
|
|
|
|
set asm-flags "-a64 -I${srcdir}/${subdir} $obj_include"
|
|
|
|
append link-flags " -m elf64lppc"
|
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
"powerpc*-*" {
|
2010-11-24 18:57:34 +01:00
|
|
|
if { [is_lp64_target] } {
|
|
|
|
set asm-arch powerpc64
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-a64 -I${srcdir}/${subdir} $obj_include"
|
2010-11-24 18:57:34 +01:00
|
|
|
append link-flags " -m elf64ppc"
|
|
|
|
} else {
|
|
|
|
set asm-arch powerpc
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-a32 -I${srcdir}/${subdir} $obj_include"
|
2010-11-24 18:57:34 +01:00
|
|
|
append link-flags " -m elf32ppc"
|
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
}
|
2003-09-15 11:52:56 +02:00
|
|
|
"sh*-*-*" {
|
|
|
|
set asm-arch sh
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gdwarf-2"
|
2003-09-15 11:52:56 +02:00
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
"sparc-*-*" {
|
|
|
|
set asm-arch sparc
|
|
|
|
}
|
|
|
|
"sparc64-*-*" {
|
|
|
|
set asm-arch sparc64
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-xarch=v9 -I${srcdir}/${subdir} $obj_include"
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gdwarf-2"
|
2003-05-07 23:51:06 +02:00
|
|
|
}
|
2006-11-22 18:19:52 +01:00
|
|
|
"spu*-*-*" {
|
|
|
|
set asm-arch spu
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-I${srcdir}/${subdir} $obj_include --no-warn"
|
2006-11-22 18:19:52 +01:00
|
|
|
set debug-flags "-gdwarf-2"
|
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
"xstormy16-*-*" {
|
|
|
|
set asm-arch xstormy16
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gdwarf-2"
|
2003-05-07 23:51:06 +02:00
|
|
|
}
|
|
|
|
"v850-*-*" {
|
|
|
|
set asm-arch v850
|
|
|
|
set gdb_wrapper_initialized 1
|
2003-03-20 13:57:48 +01:00
|
|
|
}
|
2003-07-07 16:48:50 +02:00
|
|
|
"m68k-*-*" {
|
|
|
|
set asm-arch m68k
|
|
|
|
}
|
2003-08-26 01:43:40 +02:00
|
|
|
"ia64-*-*" {
|
|
|
|
set asm-arch ia64
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gdwarf-2"
|
2003-08-26 01:43:40 +02:00
|
|
|
}
|
2005-03-08 09:59:17 +01:00
|
|
|
"iq2000-*-*" {
|
|
|
|
set asm-arch iq2000
|
|
|
|
}
|
2004-05-25 06:07:05 +02:00
|
|
|
"hppa*-linux-*" {
|
|
|
|
set asm-arch pa
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gdwarf-2"
|
2004-05-25 06:07:05 +02:00
|
|
|
}
|
2005-12-28 11:36:00 +01:00
|
|
|
"hppa-*-openbsd*" {
|
|
|
|
set asm-arch pa
|
|
|
|
set debug-flags "-gdwarf-2"
|
|
|
|
}
|
2005-04-29 16:22:28 +02:00
|
|
|
"h83*-*" {
|
|
|
|
set asm-arch h8300
|
2006-01-12 01:51:45 +01:00
|
|
|
set debug-flags "-gdwarf-2"
|
2005-04-29 16:22:28 +02:00
|
|
|
}
|
2001-11-22 02:07:24 +01:00
|
|
|
}
|
2003-05-07 23:51:06 +02:00
|
|
|
|
2000-07-04 04:47:08 +02:00
|
|
|
if { "${asm-arch}" == "" } {
|
2016-12-23 17:52:18 +01:00
|
|
|
untested "skipping tests due to no asm architecture"
|
2006-08-10 07:27:22 +02:00
|
|
|
return -1
|
1999-04-16 03:35:26 +02:00
|
|
|
}
|
|
|
|
|
2003-11-29 14:55:17 +01:00
|
|
|
# On NetBSD/ELF we need a special NetBSD-identifying note section.
|
|
|
|
if { [istarget "*-*-netbsdelf*"]
|
2006-07-29 21:15:00 +02:00
|
|
|
|| [istarget "alpha-*-netbsd*"]
|
2004-10-30 23:49:30 +02:00
|
|
|
|| [istarget "mips*-*-netbsd*"]
|
2006-05-02 00:21:35 +02:00
|
|
|
|| [istarget "powerpc-*-netbsd*"]
|
2003-11-29 14:55:17 +01:00
|
|
|
|| [istarget "x86_64-*-netbsd*"] } then {
|
|
|
|
set asm-note "netbsd"
|
|
|
|
}
|
|
|
|
|
2004-01-31 15:32:24 +01:00
|
|
|
# On OpenBSD/ELF we need a similar note section. We make no attempt
|
|
|
|
# of handing a.out here since most OpenBSD/a.out systems use a rather
|
|
|
|
# outdated assembler that doesn't assemble this test's code anyway.
|
|
|
|
if { [istarget "*-*-openbsd*"] } then {
|
|
|
|
set asm-note "openbsd"
|
|
|
|
}
|
|
|
|
|
2002-04-08 02:01:06 +02:00
|
|
|
# Watch out, we are invoking the assembler, but the testsuite sets multilib
|
|
|
|
# switches according to compiler syntax. If we pass these options straight
|
|
|
|
# to the assembler, they won't always make sense. If we don't pass them to
|
|
|
|
# the assembler, the final link will complain that the object files were
|
|
|
|
# built with different defaults. So no matter what we do, we lose. We may as
|
|
|
|
# well get out of this test sooner rather than later.
|
|
|
|
set dest [target_info name]
|
|
|
|
if [board_info $dest exists multilib_flags] {
|
|
|
|
set multilib_flags [board_info $dest multilib_flags]
|
|
|
|
if { "${multilib_flags}" != "" } {
|
2016-12-23 17:52:18 +01:00
|
|
|
untested "failed to compile"
|
2006-08-10 07:27:22 +02:00
|
|
|
return -1
|
2013-06-07 19:31:09 +02:00
|
|
|
return
|
2002-04-08 02:01:06 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-06-25 22:11:43 +02:00
|
|
|
standard_testfile asmsrc1.s asmsrc2.s
|
1999-04-16 03:35:26 +02:00
|
|
|
|
2013-08-23 22:16:58 +02:00
|
|
|
set arch_inc [standard_output_file arch.inc]
|
|
|
|
set note_inc [standard_output_file note.inc]
|
|
|
|
|
|
|
|
remote_exec build "rm -f $arch_inc"
|
|
|
|
remote_download host ${srcdir}/${subdir}/${asm-arch}.inc $arch_inc
|
|
|
|
remote_exec build "rm -f $note_inc"
|
|
|
|
remote_download host ${srcdir}/${subdir}/${asm-note}.inc $note_inc
|
2002-04-08 01:57:23 +02:00
|
|
|
|
2006-01-12 01:51:45 +01:00
|
|
|
if { [string equal ${asm-flags} ""] } {
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm-flags "-I${srcdir}/${subdir} $obj_include"
|
2006-01-12 01:51:45 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
if { [string equal ${debug-flags} ""] } {
|
2004-07-27 11:28:42 +02:00
|
|
|
set debug-flags "-gstabs"
|
2000-07-04 04:47:08 +02:00
|
|
|
}
|
1999-04-16 03:35:26 +02:00
|
|
|
|
2004-07-31 00:09:01 +02:00
|
|
|
# Allow the target board to override the debug flags.
|
2004-07-27 11:28:42 +02:00
|
|
|
if { [board_info $dest exists debug_flags] } then {
|
|
|
|
set debug-flags "[board_info $dest debug_flags]"
|
|
|
|
}
|
|
|
|
|
2004-07-31 00:09:01 +02:00
|
|
|
# The debug flags are in the format that gcc expects:
|
|
|
|
# "-gdwarf-2", "-gstabs+", or "-gstabs". To be compatible with the
|
|
|
|
# other languages in the test suite, we accept this input format.
|
|
|
|
# So the user can run the test suite with:
|
|
|
|
#
|
|
|
|
# runtest --target_board unix/gdb:debug_flags=-gdwarf-2
|
|
|
|
# make check RUNTESTFLAGS="--target_board unix/gdb:debug_flags=-gdwarf-2"
|
|
|
|
#
|
|
|
|
# However, the GNU assembler has different spellings than gcc.
|
|
|
|
# So I adjust the debug flags here.
|
|
|
|
|
|
|
|
# The GNU assembler spells "dwarf-2" as "dwarf2".
|
|
|
|
regsub "--" "-gdwarf-2" "${debug-flags}" "-gdwarf2" debug-flags
|
|
|
|
|
|
|
|
# The GNU assembler before 2.15 did not support "stabs+".
|
|
|
|
regsub "--" "-gstabs\[+\]" "${debug-flags}" "-gstabs" debug-flags
|
|
|
|
|
|
|
|
# The GNU assembler does not support level options like "-g2" or "-g3".
|
|
|
|
regsub "--" "-g\[0-9\]" "${debug-flags}" "" debug-flags
|
2004-07-27 11:28:42 +02:00
|
|
|
|
2012-06-25 22:11:43 +02:00
|
|
|
set asm1obj [standard_output_file asmrc1.o]
|
|
|
|
set asm2obj [standard_output_file asmrc2.o]
|
|
|
|
|
|
|
|
if {[target_assemble ${srcdir}/${subdir}/${srcfile} $asm1obj "${asm-flags} ${debug-flags}"] != ""} then {
|
2016-12-23 17:52:18 +01:00
|
|
|
untested "failed to assemble"
|
2006-08-10 07:27:22 +02:00
|
|
|
return -1
|
1999-04-16 03:35:26 +02:00
|
|
|
}
|
2012-06-25 22:11:43 +02:00
|
|
|
if {[target_assemble ${srcdir}/${subdir}/${srcfile2} $asm2obj "${asm-flags} ${debug-flags}"] != ""} then {
|
2016-12-23 17:52:18 +01:00
|
|
|
untested "failed to assemble"
|
2006-08-10 07:27:22 +02:00
|
|
|
return -1
|
1999-04-16 03:35:26 +02:00
|
|
|
}
|
|
|
|
|
2004-01-30 22:23:46 +01:00
|
|
|
# We deliberately don't use gdb_compile here to link together the
|
|
|
|
# assembled object files. Using gdb_compile, and therefore the C
|
|
|
|
# compiler, is conceptually wrong, since we're testing raw assembler
|
|
|
|
# code here that provides its own startup code. Using target_link
|
|
|
|
# also avoids a lot of problems on many systems, most notably on
|
|
|
|
# *-*-*bsd* and *-*-solaris2*.
|
2012-06-25 22:11:43 +02:00
|
|
|
if {[target_link [list $asm1obj $asm2obj] "${binfile}" ${link-flags}] != "" } then {
|
2016-12-23 17:52:18 +01:00
|
|
|
untested "failed to link"
|
2006-08-10 07:27:22 +02:00
|
|
|
return -1
|
1999-04-16 03:35:26 +02:00
|
|
|
}
|
|
|
|
|
2005-11-11 12:18:53 +01:00
|
|
|
# Restore the target board linker script for HC11/HC12.
|
|
|
|
if { [istarget "m6811-*-*"] || [istarget "m6812-*-*"] } {
|
|
|
|
set_board_info ldscript $old_ldscript
|
|
|
|
}
|
|
|
|
|
2007-12-22 07:44:28 +01:00
|
|
|
# Collect some line numbers.
|
2015-07-10 15:04:51 +02:00
|
|
|
set line_enter [expr [gdb_get_line_number "main enter" "asmsrc1.s"] + 1]
|
2007-12-22 07:44:28 +01:00
|
|
|
set line_main [expr [gdb_get_line_number "main start" "asmsrc1.s"] + 1]
|
|
|
|
set line_call_foo2 [expr [gdb_get_line_number "call foo2" "asmsrc1.s"] + 1]
|
|
|
|
set line_search_comment [expr [gdb_get_line_number "search" "asmsrc1.s"] + 1]
|
|
|
|
set line_foo3 [expr [gdb_get_line_number "foo3 start" "asmsrc1.s"] + 1]
|
|
|
|
set line_main_exit [expr [gdb_get_line_number "main exit" "asmsrc1.s"] + 1]
|
|
|
|
set line_foo2 [expr [gdb_get_line_number "foo2 start" "asmsrc2.s"] + 1]
|
|
|
|
set line_call_foo3 [expr [gdb_get_line_number "call foo3" "asmsrc2.s"] + 1]
|
|
|
|
set line_call_foo3_again [expr $line_call_foo3 + 1]
|
|
|
|
set line_foo2_leave [expr [gdb_get_line_number "foo2 leave" "asmsrc2.s"] + 1]
|
1999-04-16 03:35:26 +02:00
|
|
|
|
|
|
|
gdb_start
|
|
|
|
gdb_reinitialize_dir $srcdir/$subdir
|
|
|
|
gdb_load ${binfile}
|
|
|
|
|
|
|
|
#
|
|
|
|
# Run to `main' where we begin our tests.
|
|
|
|
#
|
|
|
|
|
|
|
|
if ![runto_main] then {
|
|
|
|
gdb_suppress_tests
|
|
|
|
}
|
|
|
|
|
|
|
|
# Execute the `f' command and see if the result includes source info.
|
2015-07-10 15:04:51 +02:00
|
|
|
gdb_test "f" "asmsrc1\[.\]s:$line_enter.*gdbasm_enter" "f at main"
|
|
|
|
|
|
|
|
# Execute the `n' command.
|
|
|
|
gdb_test "n" "$line_main\[ \]*.*several_nops" "n at main"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
|
|
|
# See if we properly `next' over a macro with several insns.
|
2007-12-22 07:44:28 +01:00
|
|
|
gdb_test "n" "$line_call_foo2\[ \]*.*foo2" "next over macro"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
|
|
|
# See if we can properly `step' into a subroutine call.
|
2007-12-22 07:44:28 +01:00
|
|
|
gdb_test "s" "$line_foo2\[ \]*.*" "step into foo2"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
2001-12-07 03:50:02 +01:00
|
|
|
# Test 'info target', and incidentally capture the entry point address.
|
|
|
|
set entry_point 0
|
2010-05-26 20:05:25 +02:00
|
|
|
gdb_test_multiple "info target" "info target" {
|
2001-12-07 03:50:02 +01:00
|
|
|
-re "Symbols from .*asm-source.*Entry point: 0x(\[01232456789abcdefABCDEF\]+).*$gdb_prompt $" {
|
|
|
|
set entry_point $expect_out(1,string)
|
|
|
|
pass "info target"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
# Capture the start symbol (may be '_start' or 'start')
|
|
|
|
set entry_symbol ""
|
2010-05-26 20:05:25 +02:00
|
|
|
gdb_test_multiple "info symbol 0x$entry_point" "info symbol" {
|
2002-01-18 01:13:00 +01:00
|
|
|
-re "info symbol 0x$entry_point\[\r\n\]+(\[^\r\n\]*) in section .*$gdb_prompt $" {
|
|
|
|
# We match the echoed `info symbol' command here, to help us
|
|
|
|
# reliably identify the beginning of the start symbol in the
|
|
|
|
# command's output. You might think we could just use '^' to
|
|
|
|
# start matching at the beginning of the line, but
|
|
|
|
# unfortunately, in Expect, '^' matches the beginning of the
|
|
|
|
# input that hasn't been matched by any expect clause yet. If
|
|
|
|
# every expect clause consumes a complete line, along with its
|
|
|
|
# terminating CR/LF, this is equivalent to the beginning of a
|
|
|
|
# line. But expect clauses that end with `.*' will consume as
|
|
|
|
# much as happened to arrive from the TTY --- exactly where
|
|
|
|
# they leave you depends on inter-process timing. :(
|
2001-12-07 03:50:02 +01:00
|
|
|
set entry_symbol $expect_out(1,string)
|
|
|
|
pass "info symbol"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2001-12-04 20:45:57 +01:00
|
|
|
# Now try a 'list' from the other source file.
|
2001-12-07 03:50:02 +01:00
|
|
|
gdb_test "list $entry_symbol" ".*gdbasm_startup.*" "list"
|
2001-12-04 20:45:57 +01:00
|
|
|
|
|
|
|
# Now try a source file search
|
|
|
|
gdb_test "search A routine for foo2 to call" \
|
2007-12-22 07:44:28 +01:00
|
|
|
"$line_search_comment\[ \t\]+comment \"A routine for foo2 to call.\"" "search"
|
2001-12-04 20:45:57 +01:00
|
|
|
|
1999-04-16 03:35:26 +02:00
|
|
|
# See if `f' prints the right source file.
|
2007-12-22 07:44:28 +01:00
|
|
|
gdb_test "f" ".*asmsrc2\[.\]s:$line_foo2.*" "f in foo2"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
|
|
|
# `next' one insn (or macro) to set up our stackframe (for the following bt).
|
2007-12-22 07:44:28 +01:00
|
|
|
gdb_test "n" "$line_call_foo3\[ \]*.*foo3" "n in foo2"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
2001-11-08 20:06:18 +01:00
|
|
|
# See if a simple `bt' prints the right source files and
|
|
|
|
# doesn't fall off the stack.
|
|
|
|
|
|
|
|
gdb_test "bt 10" \
|
2007-12-22 07:44:28 +01:00
|
|
|
"\#0.*foo2.*asmsrc2\[.\]s:$line_call_foo3.*\#1.*main.*asmsrc1\[.\]s:$line_call_foo2" \
|
2001-11-08 20:06:18 +01:00
|
|
|
"bt ALL in foo2"
|
2000-07-04 04:47:08 +02:00
|
|
|
|
|
|
|
# See if a capped `bt' prints the right source files.
|
2007-12-22 07:44:28 +01:00
|
|
|
gdb_test "bt 2" "\#0.*foo2.*asmsrc2\[.\]s:$line_call_foo3.*\#1.*main.*asmsrc1\[.\]s:$line_call_foo2.*" "bt 2 in foo2"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
|
|
|
# Step into another subroutine which lives back in the first source file.
|
2010-06-10 21:48:20 +02:00
|
|
|
gdb_test "s" ".*" "s 2"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
|
|
|
# Next over insns to set up the stack frame.
|
2010-06-10 21:48:20 +02:00
|
|
|
gdb_test "n" ".*" "n 2"
|
1999-04-16 03:35:26 +02:00
|
|
|
|
2000-07-04 04:47:08 +02:00
|
|
|
# Now see if a capped `bt' is correct.
|
2007-12-22 07:44:28 +01:00
|
|
|
gdb_test "bt 3" "\#0.*foo3.*asmsrc1\[.\]s:$line_foo3.*\#1.*foo2.*asmsrc2\[.\]s:$line_call_foo3.*\#2.*main.*asmsrc1\[.\]s:$line_call_foo2.*" "bt 3 in foo3"
|
2001-12-04 20:45:57 +01:00
|
|
|
|
|
|
|
# Try 'info source' from asmsrc1.s
|
|
|
|
gdb_test "info source" \
|
|
|
|
"Current source file is .*asmsrc1.s.*Source language is asm.*" \
|
|
|
|
"info source asmsrc1.s"
|
|
|
|
|
|
|
|
# Try 'finishing' from foo3
|
2010-11-24 18:57:34 +01:00
|
|
|
# Some architectures will have one or more instructions after the
|
|
|
|
# call instruction which still is part of the call sequence, so we
|
|
|
|
# must be prepared for a "finish" to show us the caller line
|
|
|
|
# again as well as the statement after.
|
|
|
|
gdb_test_multiple "finish" "finish from foo3" {
|
|
|
|
-re "Run till exit from.*\[\r\n\]$line_call_foo3\[ \t\]+gdbasm_call foo3.*$gdb_prompt $" {
|
|
|
|
pass "finish from foo3"
|
|
|
|
gdb_test "s" ".*" "s after finish"
|
|
|
|
}
|
|
|
|
-re "Run till exit from.*\[\r\n\]$line_call_foo3_again\[ \t\]+gdbasm_call foo3.*$gdb_prompt $" {
|
|
|
|
pass "finish from foo3"
|
|
|
|
}
|
|
|
|
}
|
2001-12-04 20:45:57 +01:00
|
|
|
|
|
|
|
# Try 'info source' from asmsrc2.s
|
|
|
|
gdb_test "info source" \
|
|
|
|
"Current source file is .*asmsrc2.s.*Source language is asm.*" \
|
|
|
|
"info source asmsrc2.s"
|
|
|
|
|
2002-02-21 21:58:25 +01:00
|
|
|
# Try 'info sources'. This can produce a lot of output on systems
|
|
|
|
# with dynamic linking, where the system's shared libc was compiled
|
|
|
|
# with debugging info; for example, on Linux, this produces 47kb of
|
|
|
|
# output. So we consume it as we go.
|
|
|
|
set seen_asmsrc_1 0
|
|
|
|
set seen_asmsrc_2 0
|
2010-05-26 20:05:25 +02:00
|
|
|
gdb_test_multiple "info sources" "info sources" {
|
2002-02-21 21:58:25 +01:00
|
|
|
-re "^\[^,\]*asmsrc1.s(, |\[\r\n\]+)" {
|
|
|
|
set seen_asmsrc_1 1
|
|
|
|
exp_continue
|
|
|
|
}
|
|
|
|
-re "^\[^,\]*asmsrc2.s(, |\[\r\n\]+)" {
|
|
|
|
set seen_asmsrc_2 1
|
|
|
|
exp_continue
|
|
|
|
}
|
|
|
|
-re ", " {
|
|
|
|
exp_continue
|
|
|
|
}
|
|
|
|
-re "$gdb_prompt $" {
|
|
|
|
if {$seen_asmsrc_1 && $seen_asmsrc_2} {
|
|
|
|
pass "info sources"
|
|
|
|
} else {
|
|
|
|
fail "info sources"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2001-12-04 20:45:57 +01:00
|
|
|
|
|
|
|
# Try 'info line'
|
|
|
|
gdb_test "info line" \
|
2010-11-24 18:57:34 +01:00
|
|
|
"Line $line_call_foo3_again of.*asmsrc2.s.*starts at.*<\\.?foo2+.*> and ends at.*<\\.?foo2+.*>." \
|
2001-12-04 20:45:57 +01:00
|
|
|
"info line"
|
|
|
|
|
|
|
|
# Try 'nexting' over next call to foo3
|
2007-12-22 07:44:28 +01:00
|
|
|
gdb_test "next" "$line_foo2_leave\[ \t\]+gdbasm_leave" "next over foo3"
|
2001-12-04 20:45:57 +01:00
|
|
|
|
|
|
|
# Try 'return' from foo2
|
2010-11-24 18:57:34 +01:00
|
|
|
# Like "finish", "return" command also can return to the caller
|
|
|
|
# line again or the statement after, depending on the architecture.
|
|
|
|
gdb_test_multiple "return" "return from foo2" {
|
2017-11-09 23:44:08 +01:00
|
|
|
-re "Make (foo2|selected stack frame) return now\\? .y or n. " {
|
2010-11-24 18:57:34 +01:00
|
|
|
send_gdb "y\n"
|
|
|
|
exp_continue
|
|
|
|
}
|
|
|
|
-re "\#0.*main .*$line_call_foo2\[ \t\]+gdbasm_call foo2.*$gdb_prompt $" {
|
|
|
|
pass "return from foo2"
|
|
|
|
gdb_test "s" ".*" "s after return"
|
|
|
|
}
|
|
|
|
-re "\#0.*main .*$line_main_exit\[ \t\]+gdbasm_exit0.*$gdb_prompt $" {
|
|
|
|
pass "return from foo2"
|
|
|
|
}
|
|
|
|
}
|
2001-12-04 20:45:57 +01:00
|
|
|
|
2003-05-02 01:21:08 +02:00
|
|
|
# Disassemble something, check the output
|
|
|
|
proc test_dis { command var } {
|
|
|
|
global gdb_prompt
|
2010-05-26 20:05:25 +02:00
|
|
|
gdb_test_multiple "${command}" "${command}" {
|
2003-06-01 13:37:34 +02:00
|
|
|
-re "${var}.*:.*(Cannot access|Bad address)" {
|
2003-05-02 01:21:08 +02:00
|
|
|
# The "disassembler" was only accessing the local
|
|
|
|
# executable and that would cause attempts to disassemble
|
|
|
|
# variables to fail (memory not valid).
|
|
|
|
fail "${command} (memory read error)"
|
|
|
|
}
|
|
|
|
-re "${var}.*:.*${gdb_prompt}" {
|
|
|
|
pass "${command}"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
# See if we can look at a global variable, three ways
|
Stop assuming no-debug-info variables have type int
An earlier commit made GDB no longer assume no-debug-info functions
return int. This commit gives the same treatment to variables.
Currently, you can end misled by GDB over output like this:
(gdb) p var
$1 = -1
(gdb) p /x var
$2 = 0xffffffff
until you realize that GDB is assuming that the variable is an "int",
because:
(gdb) ptype var
type = <data variable, no debug info>
You may try to fix it by casting, but that doesn't really help:
(gdb) p /x (unsigned long long) var
$3 = 0xffffffffffffffff # incorrect
^^
That's incorrect output, because the variable was defined like this:
uint64_t var = 0x7fffffffffffffff;
^^
What happened is that with the cast, GDB did an int -> 'unsigned long
long' conversion instead of reinterpreting the variable as the cast-to
type. To get at the variable properly you have to reinterpret the
variable's address manually instead, with either:
(gdb) p /x *(unsigned long long *) &var
$4 = 0x7fffffffffffffff
(gdb) p /x {unsigned long long} &var
$5 = 0x7fffffffffffffff
After this commit GDB does it for you. This is what you'll get
instead:
(gdb) p var
'var' has unknown type; cast it to its declared type
(gdb) p /x (unsigned long long) var
$1 = 0x7fffffffffffffff
As in the functions patch, the "compile" machinery doesn't currently
have the cast-to type handy, so it continues assuming no-debug
variables have int type, though now at least it warns.
The change to gdb.cp/m-static.exp deserves an explanation:
- gdb_test "print 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
+ gdb_test "print (int) 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
That's printing the "sintvar" function local static of the
"gnu_obj_1::method()" method.
The problem with that test is that that "'S::method()::static_var'"
syntax doesn't really work in C++ as you'd expect. The way to make it
work correctly currently is to quote the method part, not the whole
expression, like:
(gdb) print 'gnu_obj_1::method()'::sintvar
If you wrap the whole expression in quotes, like in m-static.exp, what
really happens is that the parser considers the whole string as a
symbol name, but there's no debug symbol with that name. However,
local statics have linkage and are given a mangled name that demangles
to the same string as the full expression, so that's what GDB prints.
After this commit, and without the cast, the print in m-static.exp
would error out saying that the variable has unknown type:
(gdb) p 'gnu_obj_1::method()::sintvar'
'gnu_obj_1::method()::sintvar' has unknown type; cast it to its declared type
TBC, if currently (even before this series) you try to print any
function local static variable of type other than int, you'll get
bogus results. You can see that with m-static.cc as is, even.
Printing the "svar" local, which is a boolean (1 byte) still prints as
"int" (4 bytes):
(gdb) p 'gnu_obj_1::method()::svar'
$1 = 1
(gdb) ptype 'gnu_obj_1::method()::svar'
type = <data variable, no debug info>
This probably prints some random bogus value on big endian machines.
If 'svar' was of some aggregate type (etc.) we'd still print it as
int, so the problem would have been more obvious... After this
commit, you'll get instead:
(gdb) p 'gnu_obj_1::method()::svar'
'gnu_obj_1::method()::svar' has unknown type; cast it to its declared type
... so at least GDB is no longer misleading. Making GDB find the real
local static debug symbol is the subject of the following patches. In
the end, it'll all "Just Work".
gdb/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* ax-gdb.c: Include "typeprint.h".
(gen_expr_for_cast): New function.
(gen_expr) <OP_CAST, OP_CAST_TYPE>: Use it.
<OP_VAR_VALUE, OP_MSYM_VAR_VALUE>: Error out if the variable's
type is unknown.
* dwarf2read.c (new_symbol_full): Fallback to int instead of
nodebug_data_symbol.
* eval.c: Include "typeprint.h".
(evaluate_subexp_standard) <OP_VAR_VALUE, OP_VAR_MSYM_VALUE>:
Error out if symbol has unknown type.
<UNOP_CAST, UNOP_CAST_TYPE>: Common bits factored out to
evaluate_subexp_for_cast.
(evaluate_subexp_for_address, evaluate_subexp_for_sizeof): Handle
OP_VAR_MSYM_VALUE.
(evaluate_subexp_for_cast): New function.
* gdbtypes.c (init_nodebug_var_type): New function.
(objfile_type): Use it to initialize types of variables with no
debug info.
* typeprint.c (error_unknown_type): New.
* typeprint.h (error_unknown_type): New declaration.
* compile/compile-c-types.c (convert_type_basic): Handle
TYPE_CODE_ERROR; warn and fallback to int for variables with
unknown type.
gdb/testsuite/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* gdb.asm/asm-source.exp: Add casts to int.
* gdb.base/nodebug.c (dataglobal8, dataglobal32_1, dataglobal32_2)
(dataglobal64_1, dataglobal64_2): New globals.
* gdb.base/nodebug.exp: Test different expressions involving the
new globals, with print, whatis and ptype. Add casts to int.
* gdb.base/solib-display.exp: Add casts to int.
* gdb.compile/compile-ifunc.exp: Expect warning. Add cast to int.
* gdb.cp/m-static.exp: Add cast to int.
* gdb.dwarf2/dw2-skip-prologue.exp: Add cast to int.
* gdb.threads/tls-nodebug.exp: Check that gdb errors out printing
tls variable with no debug info without a cast. Test with a cast
to int too.
* gdb.trace/entry-values.exp: Add casts.
2017-09-04 21:21:15 +02:00
|
|
|
gdb_test "print (int) globalvar" ".* = 11" "look at global variable"
|
2003-06-02 05:09:32 +02:00
|
|
|
test_dis "x/i &globalvar" "globalvar"
|
Stop assuming no-debug-info variables have type int
An earlier commit made GDB no longer assume no-debug-info functions
return int. This commit gives the same treatment to variables.
Currently, you can end misled by GDB over output like this:
(gdb) p var
$1 = -1
(gdb) p /x var
$2 = 0xffffffff
until you realize that GDB is assuming that the variable is an "int",
because:
(gdb) ptype var
type = <data variable, no debug info>
You may try to fix it by casting, but that doesn't really help:
(gdb) p /x (unsigned long long) var
$3 = 0xffffffffffffffff # incorrect
^^
That's incorrect output, because the variable was defined like this:
uint64_t var = 0x7fffffffffffffff;
^^
What happened is that with the cast, GDB did an int -> 'unsigned long
long' conversion instead of reinterpreting the variable as the cast-to
type. To get at the variable properly you have to reinterpret the
variable's address manually instead, with either:
(gdb) p /x *(unsigned long long *) &var
$4 = 0x7fffffffffffffff
(gdb) p /x {unsigned long long} &var
$5 = 0x7fffffffffffffff
After this commit GDB does it for you. This is what you'll get
instead:
(gdb) p var
'var' has unknown type; cast it to its declared type
(gdb) p /x (unsigned long long) var
$1 = 0x7fffffffffffffff
As in the functions patch, the "compile" machinery doesn't currently
have the cast-to type handy, so it continues assuming no-debug
variables have int type, though now at least it warns.
The change to gdb.cp/m-static.exp deserves an explanation:
- gdb_test "print 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
+ gdb_test "print (int) 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
That's printing the "sintvar" function local static of the
"gnu_obj_1::method()" method.
The problem with that test is that that "'S::method()::static_var'"
syntax doesn't really work in C++ as you'd expect. The way to make it
work correctly currently is to quote the method part, not the whole
expression, like:
(gdb) print 'gnu_obj_1::method()'::sintvar
If you wrap the whole expression in quotes, like in m-static.exp, what
really happens is that the parser considers the whole string as a
symbol name, but there's no debug symbol with that name. However,
local statics have linkage and are given a mangled name that demangles
to the same string as the full expression, so that's what GDB prints.
After this commit, and without the cast, the print in m-static.exp
would error out saying that the variable has unknown type:
(gdb) p 'gnu_obj_1::method()::sintvar'
'gnu_obj_1::method()::sintvar' has unknown type; cast it to its declared type
TBC, if currently (even before this series) you try to print any
function local static variable of type other than int, you'll get
bogus results. You can see that with m-static.cc as is, even.
Printing the "svar" local, which is a boolean (1 byte) still prints as
"int" (4 bytes):
(gdb) p 'gnu_obj_1::method()::svar'
$1 = 1
(gdb) ptype 'gnu_obj_1::method()::svar'
type = <data variable, no debug info>
This probably prints some random bogus value on big endian machines.
If 'svar' was of some aggregate type (etc.) we'd still print it as
int, so the problem would have been more obvious... After this
commit, you'll get instead:
(gdb) p 'gnu_obj_1::method()::svar'
'gnu_obj_1::method()::svar' has unknown type; cast it to its declared type
... so at least GDB is no longer misleading. Making GDB find the real
local static debug symbol is the subject of the following patches. In
the end, it'll all "Just Work".
gdb/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* ax-gdb.c: Include "typeprint.h".
(gen_expr_for_cast): New function.
(gen_expr) <OP_CAST, OP_CAST_TYPE>: Use it.
<OP_VAR_VALUE, OP_MSYM_VAR_VALUE>: Error out if the variable's
type is unknown.
* dwarf2read.c (new_symbol_full): Fallback to int instead of
nodebug_data_symbol.
* eval.c: Include "typeprint.h".
(evaluate_subexp_standard) <OP_VAR_VALUE, OP_VAR_MSYM_VALUE>:
Error out if symbol has unknown type.
<UNOP_CAST, UNOP_CAST_TYPE>: Common bits factored out to
evaluate_subexp_for_cast.
(evaluate_subexp_for_address, evaluate_subexp_for_sizeof): Handle
OP_VAR_MSYM_VALUE.
(evaluate_subexp_for_cast): New function.
* gdbtypes.c (init_nodebug_var_type): New function.
(objfile_type): Use it to initialize types of variables with no
debug info.
* typeprint.c (error_unknown_type): New.
* typeprint.h (error_unknown_type): New declaration.
* compile/compile-c-types.c (convert_type_basic): Handle
TYPE_CODE_ERROR; warn and fallback to int for variables with
unknown type.
gdb/testsuite/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* gdb.asm/asm-source.exp: Add casts to int.
* gdb.base/nodebug.c (dataglobal8, dataglobal32_1, dataglobal32_2)
(dataglobal64_1, dataglobal64_2): New globals.
* gdb.base/nodebug.exp: Test different expressions involving the
new globals, with print, whatis and ptype. Add casts to int.
* gdb.base/solib-display.exp: Add casts to int.
* gdb.compile/compile-ifunc.exp: Expect warning. Add cast to int.
* gdb.cp/m-static.exp: Add cast to int.
* gdb.dwarf2/dw2-skip-prologue.exp: Add cast to int.
* gdb.threads/tls-nodebug.exp: Check that gdb errors out printing
tls variable with no debug info without a cast. Test with a cast
to int too.
* gdb.trace/entry-values.exp: Add casts.
2017-09-04 21:21:15 +02:00
|
|
|
test_dis "disassem &globalvar, (int *) &globalvar+1" "globalvar"
|
2001-12-04 20:45:57 +01:00
|
|
|
|
2003-05-02 01:21:08 +02:00
|
|
|
# See if we can look at a static variable, three ways
|
Stop assuming no-debug-info variables have type int
An earlier commit made GDB no longer assume no-debug-info functions
return int. This commit gives the same treatment to variables.
Currently, you can end misled by GDB over output like this:
(gdb) p var
$1 = -1
(gdb) p /x var
$2 = 0xffffffff
until you realize that GDB is assuming that the variable is an "int",
because:
(gdb) ptype var
type = <data variable, no debug info>
You may try to fix it by casting, but that doesn't really help:
(gdb) p /x (unsigned long long) var
$3 = 0xffffffffffffffff # incorrect
^^
That's incorrect output, because the variable was defined like this:
uint64_t var = 0x7fffffffffffffff;
^^
What happened is that with the cast, GDB did an int -> 'unsigned long
long' conversion instead of reinterpreting the variable as the cast-to
type. To get at the variable properly you have to reinterpret the
variable's address manually instead, with either:
(gdb) p /x *(unsigned long long *) &var
$4 = 0x7fffffffffffffff
(gdb) p /x {unsigned long long} &var
$5 = 0x7fffffffffffffff
After this commit GDB does it for you. This is what you'll get
instead:
(gdb) p var
'var' has unknown type; cast it to its declared type
(gdb) p /x (unsigned long long) var
$1 = 0x7fffffffffffffff
As in the functions patch, the "compile" machinery doesn't currently
have the cast-to type handy, so it continues assuming no-debug
variables have int type, though now at least it warns.
The change to gdb.cp/m-static.exp deserves an explanation:
- gdb_test "print 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
+ gdb_test "print (int) 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
That's printing the "sintvar" function local static of the
"gnu_obj_1::method()" method.
The problem with that test is that that "'S::method()::static_var'"
syntax doesn't really work in C++ as you'd expect. The way to make it
work correctly currently is to quote the method part, not the whole
expression, like:
(gdb) print 'gnu_obj_1::method()'::sintvar
If you wrap the whole expression in quotes, like in m-static.exp, what
really happens is that the parser considers the whole string as a
symbol name, but there's no debug symbol with that name. However,
local statics have linkage and are given a mangled name that demangles
to the same string as the full expression, so that's what GDB prints.
After this commit, and without the cast, the print in m-static.exp
would error out saying that the variable has unknown type:
(gdb) p 'gnu_obj_1::method()::sintvar'
'gnu_obj_1::method()::sintvar' has unknown type; cast it to its declared type
TBC, if currently (even before this series) you try to print any
function local static variable of type other than int, you'll get
bogus results. You can see that with m-static.cc as is, even.
Printing the "svar" local, which is a boolean (1 byte) still prints as
"int" (4 bytes):
(gdb) p 'gnu_obj_1::method()::svar'
$1 = 1
(gdb) ptype 'gnu_obj_1::method()::svar'
type = <data variable, no debug info>
This probably prints some random bogus value on big endian machines.
If 'svar' was of some aggregate type (etc.) we'd still print it as
int, so the problem would have been more obvious... After this
commit, you'll get instead:
(gdb) p 'gnu_obj_1::method()::svar'
'gnu_obj_1::method()::svar' has unknown type; cast it to its declared type
... so at least GDB is no longer misleading. Making GDB find the real
local static debug symbol is the subject of the following patches. In
the end, it'll all "Just Work".
gdb/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* ax-gdb.c: Include "typeprint.h".
(gen_expr_for_cast): New function.
(gen_expr) <OP_CAST, OP_CAST_TYPE>: Use it.
<OP_VAR_VALUE, OP_MSYM_VAR_VALUE>: Error out if the variable's
type is unknown.
* dwarf2read.c (new_symbol_full): Fallback to int instead of
nodebug_data_symbol.
* eval.c: Include "typeprint.h".
(evaluate_subexp_standard) <OP_VAR_VALUE, OP_VAR_MSYM_VALUE>:
Error out if symbol has unknown type.
<UNOP_CAST, UNOP_CAST_TYPE>: Common bits factored out to
evaluate_subexp_for_cast.
(evaluate_subexp_for_address, evaluate_subexp_for_sizeof): Handle
OP_VAR_MSYM_VALUE.
(evaluate_subexp_for_cast): New function.
* gdbtypes.c (init_nodebug_var_type): New function.
(objfile_type): Use it to initialize types of variables with no
debug info.
* typeprint.c (error_unknown_type): New.
* typeprint.h (error_unknown_type): New declaration.
* compile/compile-c-types.c (convert_type_basic): Handle
TYPE_CODE_ERROR; warn and fallback to int for variables with
unknown type.
gdb/testsuite/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* gdb.asm/asm-source.exp: Add casts to int.
* gdb.base/nodebug.c (dataglobal8, dataglobal32_1, dataglobal32_2)
(dataglobal64_1, dataglobal64_2): New globals.
* gdb.base/nodebug.exp: Test different expressions involving the
new globals, with print, whatis and ptype. Add casts to int.
* gdb.base/solib-display.exp: Add casts to int.
* gdb.compile/compile-ifunc.exp: Expect warning. Add cast to int.
* gdb.cp/m-static.exp: Add cast to int.
* gdb.dwarf2/dw2-skip-prologue.exp: Add cast to int.
* gdb.threads/tls-nodebug.exp: Check that gdb errors out printing
tls variable with no debug info without a cast. Test with a cast
to int too.
* gdb.trace/entry-values.exp: Add casts.
2017-09-04 21:21:15 +02:00
|
|
|
gdb_test "print (int) staticvar" ".* = 5" "look at static variable"
|
2003-05-02 01:21:08 +02:00
|
|
|
test_dis "x/i &staticvar" "staticvar"
|
Stop assuming no-debug-info variables have type int
An earlier commit made GDB no longer assume no-debug-info functions
return int. This commit gives the same treatment to variables.
Currently, you can end misled by GDB over output like this:
(gdb) p var
$1 = -1
(gdb) p /x var
$2 = 0xffffffff
until you realize that GDB is assuming that the variable is an "int",
because:
(gdb) ptype var
type = <data variable, no debug info>
You may try to fix it by casting, but that doesn't really help:
(gdb) p /x (unsigned long long) var
$3 = 0xffffffffffffffff # incorrect
^^
That's incorrect output, because the variable was defined like this:
uint64_t var = 0x7fffffffffffffff;
^^
What happened is that with the cast, GDB did an int -> 'unsigned long
long' conversion instead of reinterpreting the variable as the cast-to
type. To get at the variable properly you have to reinterpret the
variable's address manually instead, with either:
(gdb) p /x *(unsigned long long *) &var
$4 = 0x7fffffffffffffff
(gdb) p /x {unsigned long long} &var
$5 = 0x7fffffffffffffff
After this commit GDB does it for you. This is what you'll get
instead:
(gdb) p var
'var' has unknown type; cast it to its declared type
(gdb) p /x (unsigned long long) var
$1 = 0x7fffffffffffffff
As in the functions patch, the "compile" machinery doesn't currently
have the cast-to type handy, so it continues assuming no-debug
variables have int type, though now at least it warns.
The change to gdb.cp/m-static.exp deserves an explanation:
- gdb_test "print 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
+ gdb_test "print (int) 'gnu_obj_1::method()::sintvar'" "\\$\[0-9\]+ = 4" \
That's printing the "sintvar" function local static of the
"gnu_obj_1::method()" method.
The problem with that test is that that "'S::method()::static_var'"
syntax doesn't really work in C++ as you'd expect. The way to make it
work correctly currently is to quote the method part, not the whole
expression, like:
(gdb) print 'gnu_obj_1::method()'::sintvar
If you wrap the whole expression in quotes, like in m-static.exp, what
really happens is that the parser considers the whole string as a
symbol name, but there's no debug symbol with that name. However,
local statics have linkage and are given a mangled name that demangles
to the same string as the full expression, so that's what GDB prints.
After this commit, and without the cast, the print in m-static.exp
would error out saying that the variable has unknown type:
(gdb) p 'gnu_obj_1::method()::sintvar'
'gnu_obj_1::method()::sintvar' has unknown type; cast it to its declared type
TBC, if currently (even before this series) you try to print any
function local static variable of type other than int, you'll get
bogus results. You can see that with m-static.cc as is, even.
Printing the "svar" local, which is a boolean (1 byte) still prints as
"int" (4 bytes):
(gdb) p 'gnu_obj_1::method()::svar'
$1 = 1
(gdb) ptype 'gnu_obj_1::method()::svar'
type = <data variable, no debug info>
This probably prints some random bogus value on big endian machines.
If 'svar' was of some aggregate type (etc.) we'd still print it as
int, so the problem would have been more obvious... After this
commit, you'll get instead:
(gdb) p 'gnu_obj_1::method()::svar'
'gnu_obj_1::method()::svar' has unknown type; cast it to its declared type
... so at least GDB is no longer misleading. Making GDB find the real
local static debug symbol is the subject of the following patches. In
the end, it'll all "Just Work".
gdb/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* ax-gdb.c: Include "typeprint.h".
(gen_expr_for_cast): New function.
(gen_expr) <OP_CAST, OP_CAST_TYPE>: Use it.
<OP_VAR_VALUE, OP_MSYM_VAR_VALUE>: Error out if the variable's
type is unknown.
* dwarf2read.c (new_symbol_full): Fallback to int instead of
nodebug_data_symbol.
* eval.c: Include "typeprint.h".
(evaluate_subexp_standard) <OP_VAR_VALUE, OP_VAR_MSYM_VALUE>:
Error out if symbol has unknown type.
<UNOP_CAST, UNOP_CAST_TYPE>: Common bits factored out to
evaluate_subexp_for_cast.
(evaluate_subexp_for_address, evaluate_subexp_for_sizeof): Handle
OP_VAR_MSYM_VALUE.
(evaluate_subexp_for_cast): New function.
* gdbtypes.c (init_nodebug_var_type): New function.
(objfile_type): Use it to initialize types of variables with no
debug info.
* typeprint.c (error_unknown_type): New.
* typeprint.h (error_unknown_type): New declaration.
* compile/compile-c-types.c (convert_type_basic): Handle
TYPE_CODE_ERROR; warn and fallback to int for variables with
unknown type.
gdb/testsuite/ChangeLog:
2017-09-04 Pedro Alves <palves@redhat.com>
* gdb.asm/asm-source.exp: Add casts to int.
* gdb.base/nodebug.c (dataglobal8, dataglobal32_1, dataglobal32_2)
(dataglobal64_1, dataglobal64_2): New globals.
* gdb.base/nodebug.exp: Test different expressions involving the
new globals, with print, whatis and ptype. Add casts to int.
* gdb.base/solib-display.exp: Add casts to int.
* gdb.compile/compile-ifunc.exp: Expect warning. Add cast to int.
* gdb.cp/m-static.exp: Add cast to int.
* gdb.dwarf2/dw2-skip-prologue.exp: Add cast to int.
* gdb.threads/tls-nodebug.exp: Check that gdb errors out printing
tls variable with no debug info without a cast. Test with a cast
to int too.
* gdb.trace/entry-values.exp: Add casts.
2017-09-04 21:21:15 +02:00
|
|
|
test_dis "disassem &staticvar, (int *) &staticvar+1" "staticvar"
|
2001-12-04 20:45:57 +01:00
|
|
|
|
|
|
|
# See if we can look at a static function
|
2009-10-23 02:49:33 +02:00
|
|
|
gdb_test "disassem foostatic" ".*<\\+0>:.*End of assembler dump." \
|
2001-12-04 20:45:57 +01:00
|
|
|
"look at static function"
|
|
|
|
|
2013-08-23 22:16:58 +02:00
|
|
|
remote_exec build "rm -f $arch_inc"
|
|
|
|
remote_exec build "rm -f $note_inc"
|