[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Bug libstdc++/14493] std::bad_alloc::what() does not explain what happened



https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493

--- Comment #30 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:688d126b69215db29774c249b052e52d765782b3

commit r13-6999-g688d126b69215db29774c249b052e52d765782b3
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Apr 4 12:04:14 2023 +0100

    libstdc++: Fix outdated docs about demangling exception messages

    The string returned by std::bad_exception::what() hasn't been a mangled
    name since PR libstdc++/14493 was fixed for GCC 4.2.0, so remove the
    docs showing how to demangle it.

    libstdc++-v3/ChangeLog:

            * doc/xml/manual/extensions.xml: Remove std::bad_exception from
            example program.
            * doc/html/manual/ext_demangling.html: Regenerate.

-- 
You are receiving this mail because:
You reported the bug.

Reply to: