https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107965
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- They're nothing the printers can do. You're asking to print them out before they are initialized, so they try to interpret garbage as values. The OverflowError is just because some uninitialized std::string cannot be printed. This should really be reported as a gdb bug. Gdb knows if the object's initialization had finished, so it should not try to print variables at all before their lifetime has begun, especially not via python printers. It might make sense to display the variable name with a value like <before lifetime>, but even that is debatable. The C++ standard is very clear that none of those variables exists yet at your breakpoint, and gdb contradicts its own documentation: "These are all variables (declared either static or automatic) accessible at the point of execution of the selected frame."
