https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80551
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to Segher Boessenkool from comment #5) > Why disable it? Can the feature not work, can the test not work? > > Disabling the test is papering over the problem as far as I see. The test does not work :) So should we generalize more the scanned back-trace in order to survive '#1 <null> <null>' ?
