diff options
| author | Artur Shepilko <nomadbyte@gmail.com> | 2020-04-10 10:56:43 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@polymtl.ca> | 2020-04-10 21:04:03 -0400 |
| commit | cf83625da29d1239e97f1eb4d145f347cb741889 (patch) | |
| tree | 6b707b179bb60dbfbca74a14d8fd4af0f5a7d4c9 /bfd | |
| parent | de7ac122a7f98c181c1ec175b0560bb48eabc6ea (diff) | |
| download | gdb-cf83625da29d1239e97f1eb4d145f347cb741889.zip gdb-cf83625da29d1239e97f1eb4d145f347cb741889.tar.gz gdb-cf83625da29d1239e97f1eb4d145f347cb741889.tar.bz2 | |
gdb: fix undefined behavior reported in copy_bitwise
gdb version 9.1, built with clang 8.0.0 on Ubuntu 18.04 (x86_64);
--enable-ubsan (for clang's undefined behavior sanitizer)
Executing command; `maint selftest copy_bitwise` bombs in runtime error:
../../gdb/utils.c:3432:28: runtime error: left shift of negative value -1
Closer look reveals the offending shift: `(~0 << nbits)`, apparently 0
is treated as signed int, resulting in negative complement. Explicitly
stating it unsigned 0U fixes it and the `copy_bitwise` test passes
ok.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions