aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-record.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-08-27 09:08:41 +0200
committerTom de Vries <tdevries@suse.de>2024-08-27 09:08:41 +0200
commitf6f07a0b923747af8d45c24223b66ea22f33fc97 (patch)
tree37d8e6b886d020ef1fed5c650a3c9b11cd975d88 /gdb/python/py-record.c
parentca2590d7804b4ea563eec6f1127ed17a00c30315 (diff)
downloadbinutils-f6f07a0b923747af8d45c24223b66ea22f33fc97.zip
binutils-f6f07a0b923747af8d45c24223b66ea22f33fc97.tar.gz
binutils-f6f07a0b923747af8d45c24223b66ea22f33fc97.tar.bz2
[gdb/symtab] Use [in module %s] notation more consistently in dwarf errors
In gdb/dwarf2/read.c, I found a few strings "in module %s": ... $ grep "in module %s" gdb/dwarf2/read.c | fgrep -v '[' "DIE at %s in module %s"), error (_("Dwarf Error: Dummy CU at %s referenced in module %s"), error (_("Dwarf Error: Cannot find DIE at %s referenced in module %s"), error (_("Dwarf Error: DIE at %s referenced in module %s " error (_("Dwarf Error: Dummy CU at %s referenced in module %s"), error (_("Dwarf Error: Cannot find DIE at %s referenced in module %s"), ... that are not using the commonly used "[in module %s]" notation. Fix these. In one case, the string was also used in the middle rather than at the end of the message, so fix that as well. Tested on x86_64-linux. Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/python/py-record.c')
0 files changed, 0 insertions, 0 deletions