diff options
author | Tom Tromey <tromey@adacore.com> | 2020-03-31 07:29:53 -0600 |
---|---|---|
committer | Tom Tromey <tromey@adacore.com> | 2020-03-31 07:29:53 -0600 |
commit | af62665e1339d970ab8ea3e3260dbdbde0009c2d (patch) | |
tree | 826edde9a32cce686cb46b1a89f7a341034a7d4b /gdbsupport/ChangeLog | |
parent | 16b0db75af6b4b4d434aa84c74d58b7290e04143 (diff) | |
download | binutils-gdb-af62665e1339d970ab8ea3e3260dbdbde0009c2d.tar.gz |
Don't pass NULL to memcpy in gdb
I compiled gdb with -fsanitize=undefined and ran the test suite.
A couple of reports came from passing NULL to memcpy, e.g.:
[...]btrace-common.cc:176:13: runtime error: null pointer passed as argument 2, which is declared to never be null
While it would be better to fix this in the standard, in the meantime
it seems easy to avoid this error.
gdb/ChangeLog
2020-03-31 Tom Tromey <tromey@adacore.com>
* dwarf2/abbrev.c (abbrev_table::read): Conditionally call
memcpy.
gdbsupport/ChangeLog
2020-03-31 Tom Tromey <tromey@adacore.com>
* btrace-common.cc (btrace_data_append): Conditionally call
memcpy.
Diffstat (limited to 'gdbsupport/ChangeLog')
-rw-r--r-- | gdbsupport/ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/gdbsupport/ChangeLog b/gdbsupport/ChangeLog index 1d27971f5cc..86233e8d0ef 100644 --- a/gdbsupport/ChangeLog +++ b/gdbsupport/ChangeLog @@ -1,3 +1,8 @@ +2020-03-31 Tom Tromey <tromey@adacore.com> + + * btrace-common.cc (btrace_data_append): Conditionally call + memcpy. + 2020-03-27 Andrew Burgess <andrew.burgess@embecosm.com> * create-version.sh: Resolve issues highlighted by shellcheck. |