forked from Imagelibrary/binutils-gdb
67ea24cb99
This patch started when I looked at this bit in cli/cli-cmds.c:
if (*(char **) cmd->var)
return value_cstring (*(char **) cmd->var, strlen (*(char **) cmd->var),
builtin_type (gdbarch)->builtin_char);
else
return value_cstring ("", 1,
builtin_type (gdbarch)->builtin_char);
I found it odd that the first value_cstring call passes a length that
does not consider the null terminator of the C string, but second does.
I want to clarify the documentation of value_cstring and fix the one
that is wrong.
Debugging a little bit, I found that the first call is the wrong one.
Doing:
(gdb) set args foo
(gdb) print $_gdb_setting("args")
$1 = "foo"
creates a struct value of code TYPE_CODE_ARRAY of size 3, which doesn't
have a null terminator. That does not create a valid C string. It is
however printed correctly by GDB, because the printing code makes sure
not to read past the value's length.
A way to expose the bug is to print each element of the created string,
including the null terminator. Before:
(gdb) set args foo
(gdb) p $_gdb_setting("args")[3]
no such vector element
After:
(gdb) set args foo
(gdb) p $_gdb_setting("args")[3]
$1 = 0 '\000'
Another perhaps more convincing way of showing the bug is if the string
value is passed to an inferior function call;
(gdb) print an_inferior_function($_gdb_setting("args))
The space allocate for the string in the inferior will not take into
account a null terminator (with the string "foo", 3 bytes will be
allocated). If the inferior tries to read the string until the null
terminator, it will read past the allocated buffer. Compiling the
inferior with AddressSanitizer makes that bad access obvious.
I found a few calls to value_cstring that were wrong, I fixed them
all, all exercised by the test.
The change in guile/scm-math.c maybe requires a bit of explanation.
According to the doc of gdbscm_scm_to_string, if don't pass a length
pointer, we get back a null-terminated string. If we pass a length
pointer, we get a non-null-terminated string, but we get the length
separately. Trying to pass "len + 1" to value_cstring would lead to GDB
reading past the allocated buffer, that is exactly of length `len`. So
instead, don't pass a length pointer and use strlen on the result.
gdb.base/settings.exp and gdb.python/py-mi.exp required changes in some
expected outputs, because the array type created by $_gdb_setting_str
is now one element larger, to account for the null terminator. I don't
think this change in user-visible behavior is a problem.
Change-Id: If8dd13cce55c70521e34e7c360139064b4e87496
199 lines
6.1 KiB
Plaintext
199 lines
6.1 KiB
Plaintext
# Copyright 2021 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/>.
|
|
|
|
# Test that string values are correctly allocated inside GDB when doing
|
|
# various operations that yield strings.
|
|
#
|
|
# The issue that lead to this test was a missing NULL terminator in the C-string
|
|
# values. We verify that we can print the null terminator of these strings.
|
|
|
|
load_lib "trace-support.exp"
|
|
load_lib "gdb-guile.exp"
|
|
|
|
standard_testfile
|
|
|
|
if {[build_executable "failed to prepare" $testfile $srcfile ]} {
|
|
return
|
|
}
|
|
|
|
# Check that the string contained in the convenienced variable $v is
|
|
# EXPECTED_STR.
|
|
#
|
|
# In particular, check that the null terminator is there and that we can't
|
|
# access a character past the end of the string.
|
|
|
|
proc check_v_string { expected_str } {
|
|
set len [string length $expected_str]
|
|
|
|
for { set i 0 } { $i < $len } { incr i } {
|
|
set c [string index $expected_str $i]
|
|
gdb_test "print \$v\[$i\]" "= $::decimal '$c'"
|
|
}
|
|
|
|
# Check that the string ends with a null terminator.
|
|
gdb_test "print \$v\[$i\]" {= 0 '\\000'}
|
|
|
|
# Check that we can't access a character after the end of the string.
|
|
incr i
|
|
gdb_test "print \$v\[$i\]" "no such vector element"
|
|
}
|
|
|
|
# Test with string values made by $_gdb_setting & co.
|
|
|
|
proc_with_prefix test_setting { } {
|
|
clean_restart
|
|
|
|
# This is an internal GDB implementation detail, but the variable backing a
|
|
# string setting starts as nullptr (unless explicitly initialized at startup).
|
|
# When assigning an empty value, the variable then points to an empty string.
|
|
# Test both cases, as it triggers different code paths (in addition to a
|
|
# non-empty value).
|
|
#
|
|
# Use "set trace-user" and "maintenance set test-settings string" as they are
|
|
# both not initialized at startup.
|
|
with_test_prefix "user setting" {
|
|
with_test_prefix "not set" {
|
|
foreach_with_prefix conv_func {$_gdb_setting $_gdb_setting_str} {
|
|
gdb_test_no_output "set \$v = ${conv_func}(\"trace-user\")"
|
|
check_v_string ""
|
|
}
|
|
}
|
|
|
|
with_test_prefix "set to empty" {
|
|
gdb_test "set trace-user"
|
|
foreach_with_prefix conv_func {$_gdb_setting $_gdb_setting_str} {
|
|
gdb_test_no_output "set \$v = ${conv_func}(\"trace-user\")"
|
|
check_v_string ""
|
|
}
|
|
}
|
|
|
|
with_test_prefix "set" {
|
|
gdb_test "set trace-user poulet"
|
|
foreach_with_prefix conv_func {$_gdb_setting $_gdb_setting_str} {
|
|
gdb_test_no_output {set $v = $_gdb_setting("trace-user")}
|
|
check_v_string "poulet"
|
|
}
|
|
}
|
|
}
|
|
|
|
with_test_prefix "maintenance setting" {
|
|
with_test_prefix "not set" {
|
|
foreach_with_prefix conv_func {$_gdb_maint_setting $_gdb_maint_setting_str} {
|
|
gdb_test_no_output "set \$v = ${conv_func}(\"test-settings string\")"
|
|
check_v_string ""
|
|
}
|
|
}
|
|
|
|
with_test_prefix "set to empty" {
|
|
gdb_test "maintenance set test-settings string"
|
|
foreach_with_prefix conv_func {$_gdb_maint_setting $_gdb_maint_setting_str} {
|
|
gdb_test_no_output "set \$v = ${conv_func}(\"test-settings string\")"
|
|
check_v_string ""
|
|
}
|
|
}
|
|
|
|
with_test_prefix "set" {
|
|
gdb_test "maintenance set test-settings string perchaude"
|
|
foreach_with_prefix conv_func {$_gdb_maint_setting $_gdb_maint_setting_str} {
|
|
gdb_test_no_output "set \$v = ${conv_func}(\"test-settings string\")"
|
|
check_v_string "perchaude"
|
|
}
|
|
}
|
|
}
|
|
|
|
# Test with a non-string setting, this tests yet another code path.
|
|
with_test_prefix "integer setting" {
|
|
gdb_test_no_output {set $v = $_gdb_setting_str("remotetimeout")}
|
|
check_v_string "2"
|
|
}
|
|
}
|
|
|
|
# Test with a string value created by gdb.Value in Python.
|
|
|
|
proc_with_prefix test_python_value { } {
|
|
clean_restart
|
|
|
|
if {[skip_python_tests]} {
|
|
untested "skipping test_python_value"
|
|
return
|
|
}
|
|
|
|
gdb_test_no_output "python gdb.set_convenience_variable(\"v\", \"bar\")" \
|
|
"set convenience var"
|
|
check_v_string "bar"
|
|
}
|
|
|
|
# Test with a string value created by make-value in Guile.
|
|
|
|
proc_with_prefix test_guile_value { } {
|
|
clean_restart
|
|
|
|
if {[skip_guile_tests]} {
|
|
untested "skipping test_guile_value"
|
|
return
|
|
}
|
|
|
|
# We can't set a convenience var from Guile, but we can append to history.
|
|
# Do that, then transfer to a convenience var with a CLI command.
|
|
gdb_test_no_output "guile (use-modules (gdb))"
|
|
gdb_test_multiple "guile (history-append! (make-value \"foo\"))" "make value" {
|
|
-re -wrap "($::decimal)" {
|
|
set histnum $expect_out(1,string)
|
|
}
|
|
}
|
|
|
|
gdb_test_no_output "set \$v = \$$histnum"
|
|
check_v_string "foo"
|
|
}
|
|
|
|
# Test with a string value coming from a string internal var. The only internal
|
|
# vars of this type, at the time of writing, are $trace_func and $trace_file.
|
|
# They both require inspecting a trace frame. So if the target is capable start
|
|
# tracing, record one trace frame, and use $trace_func.
|
|
|
|
proc_with_prefix test_internal_var { } {
|
|
if {![gdb_trace_common_supports_arch]} {
|
|
unsupported "arch does not support trace"
|
|
return
|
|
}
|
|
|
|
clean_restart $::binfile
|
|
|
|
if {![runto_main]} {
|
|
fail "could not run to main"
|
|
return
|
|
}
|
|
|
|
if {![gdb_target_supports_trace]} {
|
|
unsupported "target does not support trace"
|
|
return
|
|
}
|
|
|
|
gdb_test "break end" "Breakpoint $::decimal at $::hex.*"
|
|
gdb_test "trace trace_me" "Tracepoint $::decimal at $::hex.*"
|
|
gdb_test_no_output "tstart"
|
|
gdb_test "continue" "Breakpoint $::decimal, end.*"
|
|
gdb_test_no_output "tstop"
|
|
gdb_test "tfind" "Found trace frame 0, tracepoint $::decimal.*"
|
|
gdb_test_no_output "set \$v = \$trace_func"
|
|
gdb_test "tfind none" "No longer looking at any trace frame.*"
|
|
check_v_string "trace_me"
|
|
}
|
|
|
|
test_setting
|
|
test_python_value
|
|
test_guile_value
|
|
test_internal_var
|