* [PATCH 1/2] gdb: Avoid undefined shifts
2022-04-01 20:22 [PATCH 0/2] Fix a couple undefined behaviors flagged by UBSan Pedro Alves
@ 2022-04-01 20:22 ` Pedro Alves
2022-04-04 12:16 ` Pedro Alves
2022-04-01 20:22 ` [PATCH 2/2] Avoid undefined behavior in gdbscm_make_breakpoint Pedro Alves
1 sibling, 1 reply; 4+ messages in thread
From: Pedro Alves @ 2022-04-01 20:22 UTC (permalink / raw)
To: gdb-patches
I noticed that a build of GDB with GCC + --enable-ubsan, testing
against GDBserver showed this GDB crash:
(gdb) PASS: gdb.trace/trace-condition.exp: trace: 0x00abababcdcdcdcd << 46 == 0x7373400000000000: advance to trace begin
tstart
../../src/gdb/valarith.c:1365:15: runtime error: left shift of 48320975398096333 by 46 places cannot be represented in type 'long int'
ERROR: GDB process no longer exists
GDB process exited with wait status 269549 exp9 0 1
UNRESOLVED: gdb.trace/trace-condition.exp: trace: 0x00abababcdcdcdcd << 46 == 0x7373400000000000: start trace experiment
The problem is that, "0x00abababcdcdcdcd << 46" is an undefined signed
left shift, because the result is not representable in the type of the
lhs, which is signed. This actually became defined in C++20, and if
you compile with "g++ -std=c++20 -Wall", you'll see that GCC no longer
warns about it, while it warns if you specify prior language versions.
While at it, there are a couple other situations that are undefined
(and are still undefined in C++20) and result in GDB dying: shifting
by a negative ammount, or by >= than the bit size of the promoted lhs.
For the latter, GDB shifts using (U)LONGEST internally, so you have to
shift by >= 64 bits to see it:
$ gdb --batch -q -ex "p 1 << -1"
../../src/gdb/valarith.c:1365:15: runtime error: shift exponent -1 is negative
$ # gdb exited
$ gdb --batch -q -ex "p 1 << 64"
../../src/gdb/valarith.c:1365:15: runtime error: shift exponent 64 is too large for 64-bit type 'long int'
$ # gdb exited
Also, right shifting a negative value is implementation-defined
(before C++20, after which it is defined). For this, I chose to
change nothing in GDB other than adding tests, as I don't really know
whether we need to do anything. AFAIK, most implementations do an
arithmetic right shift, and it may be we don't support any host or
target that behaves differently. Plus, this becomes defined in C++20
exactly as arithmetic right shift.
Compilers don't error out on such shifts, at best they warn, so I
think GDB should just continue doing the shifts anyhow too.
Thus:
- Adjust scalar_binop to avoid the undefined paths, either by adding
explicit result paths, or by casting the lhs of the left shift to
unsigned, as appropriate. For the shifts by negative amount or a
too-large amount, I made the result be 0 (and warn). This is
undefined, so we're free to pick any value, and 0 seems reasonable.
- Make GDB warn for the cases that are still undefined in C++20. The
warnings' texts are same as what GCC prints.
- Add comprehensive tests to gdb.base/bitops.exp, so that we exercise
all these scenarios.
Change-Id: I8bcd5fa02de3114b7ababc03e65702d86ec8d45d
---
gdb/testsuite/gdb.base/bitops.exp | 139 ++++++++++++++++++++++++++++++
gdb/valarith.c | 61 ++++++++++++-
2 files changed, 196 insertions(+), 4 deletions(-)
diff --git a/gdb/testsuite/gdb.base/bitops.exp b/gdb/testsuite/gdb.base/bitops.exp
index deea456710f..2ccfd4834ec 100644
--- a/gdb/testsuite/gdb.base/bitops.exp
+++ b/gdb/testsuite/gdb.base/bitops.exp
@@ -110,3 +110,142 @@ gdb_test "print 0 || 1 && 0 | 0 ^ 0 == 8" ".\[0-9\]* = 0" \
gdb_test "print 0 == 8 > 128 >> 1 + 2 * 2" ".\[0-9\]* = 0" \
"print value of 0 == 8 > 128 >> 1 + 2 * 2"
+# Test a print command that prints out RESULT_RE. If WARNING is
+# non-empty, it is expected that GDB prints this warning before the
+# print result. If WARNING is empty, it is expected that GDB prints
+# text other than the print result.
+proc test_shift {cmd result_re {warning ""}} {
+ if {$warning != ""} {
+ set warning_re "[string_to_regexp $warning]\r\n"
+ } else {
+ set warning_re ""
+ }
+
+ set cmd_re [string_to_regexp $cmd]
+
+ gdb_test_multiple $cmd "" {
+ -re -wrap "^$cmd_re\r\n$warning_re\\$$::decimal$result_re" {
+ pass $gdb_test_name
+ }
+ }
+}
+
+# Test a print command that issues a warning about the right shift
+# count being negative. The "ne" suffix stands for negative.
+proc test_shift_ne {cmd result} {
+ test_shift $cmd $result "warning: right shift count is negative"
+}
+
+# Test a print command that issues a warning about the right shift
+# count being too large. The "lt" suffix stands for "too large".
+proc test_shift_tl {cmd result} {
+ test_shift $cmd $result "warning: right shift count >= width of type"
+}
+
+# Make sure a signed left shift that overflows, i.e., whose result
+# isn't representable in the signed type of the lhs, which is actually
+# undefined, doesn't crash GDB when is it built with UBSan.
+
+test_shift "print /x 0x0fffffffffffffff << 8" " = 0xffffffffffffff00"
+test_shift "print /x 0x0fffffff << 8" " = 0xffffff00"
+
+# Make sure the result is still signed when the lhs was signed.
+test_shift "print 0x0fffffffffffffff << 8" " = -256"
+test_shift "print 0x0fffffff << 8" " = -256"
+
+# 8-bit and 16-bit are promoted to int.
+foreach sign {"signed" "unsigned"} {
+ test_shift "print /x ($sign char) 0x0f << 8" " = 0xf00"
+ test_shift "print ($sign char) 0x0f << 8" " = 3840"
+ test_shift "print /x ($sign short) 0x0fff << 8" " = 0xfff00"
+ test_shift "print ($sign short) 0x0fff << 8" " = 1048320"
+}
+
+# Similarly, test shifting with both negative and too-large rhs. Both
+# cases are undefined, but GDB lets them go through anyhow, similarly
+# to how compilers don't error out. Try both signed and unsigned lhs.
+
+# 8-bit lhs, signed and unsigned. These get promoted to 32-bit int.
+foreach lhs {"(signed char) 0x7f" "(unsigned char) 0xff"} {
+ test_shift_ne "print $lhs << -1" " = 0"
+ test_shift_ne "print $lhs >> -1" " = 0"
+
+ test_shift "print/x $lhs >> 8" " = 0x0"
+ test_shift "print/x $lhs << 8" " = 0x(7|f)f00"
+
+ test_shift_tl "print $lhs >> 32" " = 0"
+ test_shift_tl "print $lhs << 32" " = 0"
+ test_shift_tl "print $lhs >> 33" " = 0"
+ test_shift_tl "print $lhs << 33" " = 0"
+}
+
+# 16-bit lhs, signed and unsigned. These get promoted to 32-bit int.
+foreach {lhs_cast lhs_val} {
+ "(short)" "0x7fff"
+ "(unsigned short)" "0xffff"
+} {
+ set lhs "$lhs_cast $lhs_val"
+
+ test_shift_ne "print $lhs << -1" " = 0"
+ test_shift_ne "print $lhs >> -1" " = 0"
+
+ # Confirm shifting by 0 doesn't warn.
+ test_shift "print/x $lhs << 0" " = $lhs_val"
+ test_shift "print/x $lhs >> 0" " = $lhs_val"
+
+ # These don't overflow due to promotion.
+ test_shift "print/x $lhs >> 16" " = 0x0"
+ test_shift "print/x $lhs << 16" " = 0x(7|f)fff0000"
+
+ test_shift_tl "print $lhs >> 32" " = 0"
+ test_shift_tl "print $lhs << 32" " = 0"
+ test_shift_tl "print $lhs >> 33" " = 0"
+ test_shift_tl "print $lhs << 33" " = 0"
+}
+
+# 32-bit lhs, signed and unsigned.
+foreach lhs {0x7fffffff 0xffffffff} {
+ test_shift_ne "print $lhs << -1" " = 0"
+ test_shift_ne "print $lhs >> -1" " = 0"
+
+ # Confirm shifting by 0 doesn't warn.
+ test_shift "print/x $lhs << 0" " = $lhs"
+ test_shift "print/x $lhs >> 0" " = $lhs"
+
+ test_shift_tl "print $lhs >> 32" " = 0"
+ test_shift_tl "print $lhs << 32" " = 0"
+
+ test_shift_tl "print $lhs >> 33" " = 0"
+ test_shift_tl "print $lhs << 33" " = 0"
+}
+
+# 64-bit lhs, signed and unsigned.
+foreach lhs {0x7fffffffffffffff 0xffffffffffffffff} {
+ test_shift_ne "print $lhs >> -1" " = 0"
+ test_shift_ne "print $lhs << -1" " = 0"
+
+ # Confirm shifting by 0 doesn't warn.
+ test_shift "print/x $lhs << 0" " = $lhs"
+ test_shift "print/x $lhs >> 0" " = $lhs"
+
+ test_shift_tl "print $lhs >> 64" " = 0"
+ test_shift_tl "print $lhs << 64" " = 0"
+
+ test_shift_tl "print $lhs >> 65" " = 0"
+ test_shift_tl "print $lhs << 65" " = 0"
+}
+
+# Right shift a negative number by a negative amount.
+test_shift_ne "print -1 >> -1" " = 0"
+
+# Check right shifting a negative value. This is
+# implementation-defined, up until C++20. In most implementations,
+# this performs an arithmetic right shift, so that the result remains
+# negative. Currently, GDB does whatever the host's compiler does.
+# If that turns out wrong for some host/target, then GDB should be
+# taught to ask the target gdbarch what to do.
+test_shift "print -1 >> 0" " = -1"
+test_shift "print -1 >> 1" " = -1"
+test_shift "print -8 >> 1" " = -4"
+test_shift "print -8l >> 1" " = -4"
+test_shift "print -8ll >> 1" " = -4"
diff --git a/gdb/valarith.c b/gdb/valarith.c
index 36d30f161f6..d2e6444da2a 100644
--- a/gdb/valarith.c
+++ b/gdb/valarith.c
@@ -1070,6 +1070,39 @@ complex_binop (struct value *arg1, struct value *arg2, enum exp_opcode op)
return value_literal_complex (result_real, result_imag, result_type);
}
+/* Return the type's length in bits. */
+
+static int
+type_length_bits (type *type)
+{
+ int unit_size = gdbarch_addressable_memory_unit_size (type->arch ());
+ return unit_size * 8 * TYPE_LENGTH (type);
+}
+
+/* Check whether the the RHS value of a shift is valid. RHS_VAL is
+ the shift amount, and RESULT_TYPE is result type. This is used to
+ avoid both negative or too-large shift amounts, which are
+ undefined, and would crash a GDB built with UBSan. Warns and
+ returns false if not valid, and returns true if not valid. */
+
+static bool
+check_valid_shift_rhs (type *result_type, LONGEST rhs_val)
+{
+ if (rhs_val < 0)
+ {
+ warning (_("right shift count is negative"));
+ return false;
+ }
+
+ if (rhs_val >= type_length_bits (result_type))
+ {
+ warning (_("right shift count >= width of type"));
+ return false;
+ }
+
+ return true;
+}
+
/* Perform a binary operation on two operands which have reasonable
representations as integers or floats. This includes booleans,
characters, integers, or floats.
@@ -1233,11 +1266,17 @@ scalar_binop (struct value *arg1, struct value *arg2, enum exp_opcode op)
break;
case BINOP_LSH:
- v = v1 << v2;
+ if (!check_valid_shift_rhs (result_type, v2))
+ v = 0;
+ else
+ v = v1 << v2;
break;
case BINOP_RSH:
- v = v1 >> v2;
+ if (!check_valid_shift_rhs (result_type, v2))
+ v = 0;
+ else
+ v = v1 >> v2;
break;
case BINOP_BITWISE_AND:
@@ -1362,11 +1401,25 @@ scalar_binop (struct value *arg1, struct value *arg2, enum exp_opcode op)
break;
case BINOP_LSH:
- v = v1 << v2;
+ if (!check_valid_shift_rhs (result_type, v2))
+ v = 0;
+ else
+ {
+ /* Cast to unsigned to avoid undefined behavior on
+ signed shift overflow (unless C++20 or later),
+ which would crash GDB when built with UBSan.
+ Note We don't warn on left signed shift overflow,
+ because starting with C++20, that is actually
+ defined behavior. */
+ v = (ULONGEST) v1 << v2;
+ }
break;
case BINOP_RSH:
- v = v1 >> v2;
+ if (!check_valid_shift_rhs (result_type, v2))
+ v = 0;
+ else
+ v = v1 >> v2;
break;
case BINOP_BITWISE_AND:
--
2.26.2
^ permalink raw reply [flat|nested] 4+ messages in thread* [PATCH 2/2] Avoid undefined behavior in gdbscm_make_breakpoint
2022-04-01 20:22 [PATCH 0/2] Fix a couple undefined behaviors flagged by UBSan Pedro Alves
2022-04-01 20:22 ` [PATCH 1/2] gdb: Avoid undefined shifts Pedro Alves
@ 2022-04-01 20:22 ` Pedro Alves
1 sibling, 0 replies; 4+ messages in thread
From: Pedro Alves @ 2022-04-01 20:22 UTC (permalink / raw)
To: gdb-patches
Running gdb.guile/scm-breakpoint.exp against an --enable-ubsan build,
we see:
UNRESOLVED: gdb.guile/scm-breakpoint.exp: test_watchpoints: create a breakpoint with an invalid type number
...
guile (define wp2 (make-breakpoint "result" #:wp-class WP_WRITE #:type 999))
../../src/gdb/guile/scm-breakpoint.c:377:11: runtime error: load of value 999, which is not a valid value for type 'bptype'
ERROR: GDB process no longer exists
Fix this by parsing the user/guile input as plain int, and cast to
internal type only after we know we have a number that would be valid.
Change-Id: I03578d07db00be01b610a8f5ce72e5521aea6a4b
---
gdb/guile/scm-breakpoint.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/gdb/guile/scm-breakpoint.c b/gdb/guile/scm-breakpoint.c
index 0069d3371ff..d6c89aa8c71 100644
--- a/gdb/guile/scm-breakpoint.c
+++ b/gdb/guile/scm-breakpoint.c
@@ -353,8 +353,8 @@ gdbscm_make_breakpoint (SCM location_scm, SCM rest)
char *location;
int type_arg_pos = -1, access_type_arg_pos = -1,
internal_arg_pos = -1, temporary_arg_pos = -1;
- enum bptype type = bp_breakpoint;
- enum target_hw_bp_type access_type = hw_write;
+ int type = bp_breakpoint;
+ int access_type = hw_write;
int internal = 0;
int temporary = 0;
SCM result;
@@ -403,7 +403,7 @@ gdbscm_make_breakpoint (SCM location_scm, SCM rest)
case bp_access_watchpoint:
case bp_catchpoint:
{
- const char *type_name = bpscm_type_to_string (type);
+ const char *type_name = bpscm_type_to_string ((enum bptype) type);
gdbscm_misc_error (FUNC_NAME, type_arg_pos,
gdbscm_scm_from_c_string (type_name),
_("unsupported breakpoint type"));
@@ -417,8 +417,8 @@ gdbscm_make_breakpoint (SCM location_scm, SCM rest)
bp_smob->is_scheme_bkpt = 1;
bp_smob->spec.location = location;
- bp_smob->spec.type = type;
- bp_smob->spec.access_type = access_type;
+ bp_smob->spec.type = (enum bptype) type;
+ bp_smob->spec.access_type = (enum target_hw_bp_type) access_type;
bp_smob->spec.is_internal = internal;
bp_smob->spec.is_temporary = temporary;
--
2.26.2
^ permalink raw reply [flat|nested] 4+ messages in thread