diff options
author | Alan Modra <amodra@gmail.com> | 2025-01-01 22:31:50 +1030 |
---|---|---|
committer | Alan Modra <amodra@gmail.com> | 2025-01-01 22:31:50 +1030 |
commit | b38cf91f230bc3892ab9c3deb4f1b6639c657c47 (patch) | |
tree | 5cfd11814669a298c822cffe2eda3bc1ea1cad4c /gdb/testsuite/gdb.python/py-commands-breakpoint.py | |
parent | 5e04003fac2f15d18ec8c9167c139582fb897728 (diff) | |
download | binutils-b38cf91f230bc3892ab9c3deb4f1b6639c657c47.zip binutils-b38cf91f230bc3892ab9c3deb4f1b6639c657c47.tar.gz binutils-b38cf91f230bc3892ab9c3deb4f1b6639c657c47.tar.bz2 |
PR 32507, PRIx64 in error messages on 32-bit mingw
People, including me, had forgotten that the bfd_error_handler just
handled standard printf format strings, not MSC %I64 and suchlike.
Using PRIx64 and similar in errors does not work if the host compiler
headers define those formats as the Microsoft %I64 variety. (We
handled %ll OK, editing it to %I64 on such hosts.)
PR 32507
* bfd.c (_bfd_doprnt, _bfd_doprnt_scan): Handle %I64 and %I32
in input strings if the host defines PRId64 as "I64d".
Edit %ll to %I64 on detecting PRId64 as "I64d" rather than on
a preprocessor define.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-commands-breakpoint.py')
0 files changed, 0 insertions, 0 deletions