https://gcc.gnu.org/bugzilla/show_bug.cgi?id=125312
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- Yeah I saw that, but it doesn't tell us anything useful. Probably because Windows. If a __glibcxx_assert or _GLIBCXX_DEBUG assertion fails, it's supposed to print out a message along with the enclosing function name, file name, line number, etc.
