diff options
| author | Tom Tromey <tom@tromey.com> | 2018-07-29 17:16:03 -0600 |
|---|---|---|
| committer | Tom Tromey <tom@tromey.com> | 2018-10-03 15:19:06 -0600 |
| commit | 0101665f864383147448c5871a67286a3f7a9a28 (patch) | |
| tree | dd4ce1e0693c6756fd37ca693294abf8dc7fca1b /gdb/parse.c | |
| parent | ad69edbb4b230582ecd1863e68d0c2044f5ad901 (diff) | |
| download | binutils-0101665f864383147448c5871a67286a3f7a9a28.zip binutils-0101665f864383147448c5871a67286a3f7a9a28.tar.gz binutils-0101665f864383147448c5871a67286a3f7a9a28.tar.bz2 | |
Avoid undefined behavior in extract_integer
-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.)
gdb/ChangeLog
2018-10-03 Tom Tromey <tom@tromey.com>
* findvar.c (extract_integer): Do work in an unsigned type.
Diffstat (limited to 'gdb/parse.c')
0 files changed, 0 insertions, 0 deletions