https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58123
--- Comment #8 from Jan Kratochvil <jan.kratochvil at redhat dot com> --- (In reply to Aldy Hernandez from comment #7) > Putting this aside for a second, my question is, do we really want a > debugging experience where we jump from back from the end of scope, back to > the declaration of the class? I do not think so. Or if so then the destructor call needs to be marked with is_stmt=false; but GDB currently ignores is_stmt. It would then show the declaration line during backtrace from crashed destructor (I am not sure it would be better than the 4.7 last statement of the block).
