diff options
| author | Kevin Buettner <kevinb@redhat.com> | 2020-08-05 18:29:33 -0700 |
|---|---|---|
| committer | Kevin Buettner <kevinb@redhat.com> | 2020-08-05 18:57:53 -0700 |
| commit | b5582ab72f025c54d4a6e8f459f78a8c92e6df29 (patch) | |
| tree | e58877697b0a5bb84d139373ba21d39eff8cfdd8 /ld | |
| parent | f5750f89e3c5447027f29881e5484e1fda83912b (diff) | |
| download | gdb-b5582ab72f025c54d4a6e8f459f78a8c92e6df29.zip gdb-b5582ab72f025c54d4a6e8f459f78a8c92e6df29.tar.gz gdb-b5582ab72f025c54d4a6e8f459f78a8c92e6df29.tar.bz2 | |
Don't output null pathname in core_target::build_file_mappings warning
While looking into the regressions reported by Luis Machado, I noticed
that null pathnames were being output in the warnings. E.g.
warning: Can't open file (null) during file-backed mapping note processing
I've changed the warning to output the pathname found in the note,
like this:
warning: Can't open file /var/lib/docker/aufs/diff/d07c...e21/lib/x86_64-linux-gnu/libc-2.27.so during file-backed mapping note processing
(I've shortened one of the path elements above.)
gdb/ChangeLog:
* corelow.c (core_target::build_file_mappings): Don't output
null pathname in warning.
Diffstat (limited to 'ld')
0 files changed, 0 insertions, 0 deletions