[v2,04/10] Avoid undefined behavior in extract_integer

Message ID 20180830024416.23386-5-tom@tromey.com
State Superseded
Headers show
  • Enable undefined behavior sanitizer
Related show

Commit Message

Tom Tromey Aug. 30, 2018, 2:44 a.m.
-fsanitize=undefined showed that extract_integer could left-shift a
negative value, which is undefined.  This patch fixes the problem by
doing all the work in an unsigned type.  This relies on
implementation-defined behavior, but I tend to think we are on safe
ground there.  (Also, if need be, violations of this could probably be
detected, either by configure or by a static_assert.)

2018-08-29  Tom Tromey  <tom@tromey.com>

	* findvar.c (extract_integer): Do work in an unsigned type.
 gdb/ChangeLog | 4 ++++
 gdb/findvar.c | 2 +-
 2 files changed, 5 insertions(+), 1 deletion(-)



diff --git a/gdb/findvar.c b/gdb/findvar.c
index 9256833ab60..be6c9d6f60b 100644
--- a/gdb/findvar.c
+++ b/gdb/findvar.c
@@ -50,7 +50,7 @@  template<typename T, typename>
 extract_integer (const gdb_byte *addr, int len, enum bfd_endian byte_order)
-  T retval = 0;
+  typename std::make_unsigned<T>::type retval = 0;
   const unsigned char *p;
   const unsigned char *startaddr = addr;
   const unsigned char *endaddr = startaddr + len;