diff options
author | Alan Modra <amodra@gmail.com> | 2017-09-26 09:38:26 +0930 |
---|---|---|
committer | Alan Modra <amodra@gmail.com> | 2017-09-26 09:38:26 +0930 |
commit | a54018b72d75abf2e74bf36016702da06399c1d9 (patch) | |
tree | 15423d9f75dddce78a6784d0fc43f13e97e3d6b9 /COPYING3 | |
parent | e338894dc2e603683bed2172e8e9f25b29051005 (diff) | |
download | gdb-a54018b72d75abf2e74bf36016702da06399c1d9.zip gdb-a54018b72d75abf2e74bf36016702da06399c1d9.tar.gz gdb-a54018b72d75abf2e74bf36016702da06399c1d9.tar.bz2 |
PR22205, .debug_line file table NULL filename
The PR22200 fuzzer testcase found one way to put NULLs into .debug_line
file tables. PR22205 finds another. This patch gives up on trying to
prevent NULL files in the file table and instead just copes with them.
Arguably, this is better than giving up and showing no info from
.debug_line. I've also fixed a case where the fairly recent DWARF5
support in handling broken DWARG could result in uninitialized memory
reads, and made a small tidy.
PR 22205
* dwarf2.c (concat_filename): Return "<unknown>" on NULL filename.
(read_formatted_entries): Init "fe".
(decode_line_info <DW_LNE_define_file>): Use line_info_add_file_name.
Diffstat (limited to 'COPYING3')
0 files changed, 0 insertions, 0 deletions