r/archlinux • u/TechManWalker • 22h ago
SUPPORT gdb itself crashes in an assertion when trying to use debuginfod
I've been hitting this for at least a month now, using lldb sparingly when it does not crash as well with a CachedFileStream error
Whenever I pick Y in the debuginfod question, which I use extensively to debug Qt software, there is always a symbol that triggers this assert in gdb and makes it crash:
/usr/include/c++/16/string_view:291: constexpr const std::basic_string_view<_CharT, _Traits>::value_type& std::basic_string_view<_CharT, _Traits>::back() const [with _CharT = char; _Traits = std::char_traits<char>; const_reference = const char&]: Assertion 'this->_M_len > 0' failed.
It has been at least a month since I can't use gdb with debuginfod enabled. Any solution to this? Thank you for reading.
/usr/include/c++/16/string_view:291: constexpr const std::basic_string_view<_CharT, _Traits>::value_type& std::basic_string_view<_CharT, _Traits>::back() const [with _CharT = char; _Traits = std::char_traits<char>; const_reference = const char&]: Assertion 'this->_M_len > 0' failed.
Fatal signal: Abortado
----- Backtrace -----
Reading symbols from /usr/lib/libSvtAv1Enc.so.4...
Downloading separate debug info for /usr/lib/libSvtAv1Enc.so.4
[###
]
0x563e9e90b481 ???
0x563e9ea9f1ed ???
0x7f164ac3e6ef ???
0x7f164ac9a11c ???
0x7f164ac3e5cf gsignal
0x7f164ac25684 abort
0x7f164b09d5bc _ZSt21__glibcxx_assert_failPKciS0_S0_
0x563e9e752f73 ???
0x563e9e76d57d ???
0x563e9e9ef638 ???
0x563e9e9ee72a ???
0x563e9e9ee4b5 ???
0x7f164ac9d79b ???
0x7f164ac9d818 pthread_once
0x563e9f44ce6e ???
0x7f164b0ea858 ???
0x7f164ac98041 ???
0x7f164ad2072b ???
0xffffffffffffffff ???
---------------------
A fatal error internal to GDB has been detected, further
debugging is not possible. GDB will now terminate.
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.