espressif/binutils-gdb
1
0
Fork 0
mirror of https://github.com/espressif/binutils-gdb.git synced 2025-05-31 18:20:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

Don't output null pathname in core_target::build_file_mappings warning

Browse Source 
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.
This commit is contained in:
Kevin Buettner
2020-08-05 18:29:33 -07:00
parent f5750f89e3
commit b5582ab72f
2 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/ChangeLog
View File

@ -1,3 +1,8 @@
2020-08-05 Kevin Buettner <kevinb@redhat.com>
* corelow.c (core_target::build_file_mappings): Don't output
null pathname in warning.
2020-08-05 Simon Marchi <simon.marchi@polymtl.ca>
* gdb.dwarf2/clztest.exp, gdb.dwarf2/dw2-common-block.exp,

2
gdb/corelow.c
View File

@ -218,7 +218,7 @@ core_target::build_file_mappings ()
{
warning (_("Can't open file %s during file-backed mapping "
"note processing"),
expanded_fname.get ());
filename);
return;
}