On Mon, 2017-01-16 at 11:55 +0100, Miklos Vajna wrote: > "catch throw" and "continue". Hopefully that'll show us where > std::bad_alloc is thrown.
last time I checked, I was successful with catch throw std::bad_alloc but there's a bunch of caveats on catching exceptions by pattern in gdb, so your milage may vary there. C. _______________________________________________ LibreOffice mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice
