aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree.cc
diff options
context:
space:
mode:
authorJonathan Wakely <jwakely@redhat.com>2022-02-17 17:23:36 +0000
committerJonathan Wakely <jwakely@redhat.com>2022-02-17 22:22:14 +0000
commit36100e0e952b92a6cd819620fcef851f0069ac8f (patch)
tree267c3b8f63da661fc3b8accc505cbd5b85cc612c /gcc/tree.cc
parentc352ef0ed90cfc07d494dfec111121bc683e337b (diff)
downloadgcc-36100e0e952b92a6cd819620fcef851f0069ac8f.zip
gcc-36100e0e952b92a6cd819620fcef851f0069ac8f.tar.gz
gcc-36100e0e952b92a6cd819620fcef851f0069ac8f.tar.bz2
libstdc++: Make std::error_code printer more robust
This attempts to implement a partial workaround for the GDB bug https://sourceware.org/bugzilla/show_bug.cgi?id=28856 which causes GDB to crash when printing a frame with a std::error_code argument. By recognising the known error categories defined in the library and hardcoding their names we do not need to call cat->name() on the category. This has the additional benefit of also working when debugging a core file rather than a running process. For those known categories we can also cast the int value to the corresponding error code enum (e.g. future_errc) so that we show an enumerator instead of just an integer. For program-defined categories we just use the name of the dynamic type to identify the category, and print the value as an integer. Once the GDB bug is fixed and the virtual name() function can be called safely, that would be preferable. For now it's better to have an imperfect printer that doesn't crash GDB. This rewritten StdErrorCodePrinter needs gdb.Value.dynamic_type, so is only registered if that is supported, which means GDB 7.7 and later. libstdc++-v3/ChangeLog: * python/libstdcxx/v6/printers.py (StdErrorCodePrinter): Replace code that call cat->name() on std::error_category objects. Identify known categories by symbol name and use a hardcoded name. Print error code values as enumerators where appopriate. * testsuite/libstdc++-prettyprinters/cxx11.cc: Adjust expected name of custom category. Check io_errc and future_errc errors.
Diffstat (limited to 'gcc/tree.cc')
0 files changed, 0 insertions, 0 deletions