diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2018-10-04 22:43:27 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2018-10-04 22:59:44 -0400 |
| commit | 1f88d0c87c37d3a15fa6376335e8b0d1c79d85aa (patch) | |
| tree | 211de0a181fb8d8f6ea030ab839fd6bc8d9e0869 /gdb/arch/amd64.h | |
| parent | 1f041c6edf49a896b99db253066fce427a7d2264 (diff) | |
| download | gdb-1f88d0c87c37d3a15fa6376335e8b0d1c79d85aa.zip gdb-1f88d0c87c37d3a15fa6376335e8b0d1c79d85aa.tar.gz gdb-1f88d0c87c37d3a15fa6376335e8b0d1c79d85aa.tar.bz2 | |
Fix undefined behavior, don't pass NULL to fwrite
If a vector that we try to write using file_write is empty, we may end
up passing NULL to fwrite, which triggers UBSan:
.../gdb/dwarf-index-write.c:73:14: runtime error: null pointer passed as argument 1, which is declared to never be null
Avoid it by skipping the write if the vector is empty.
gdb/ChangeLog:
* dwarf-index-write.c (file_write): Don't write if the vector is
empty.
Diffstat (limited to 'gdb/arch/amd64.h')
0 files changed, 0 insertions, 0 deletions