Surely the cheapest call-site check for the result of malloc() is just
to attempt a fetch from the memory location?
That will trigger SIGSEGV, but at least you'll get a stack-trace out of it.
On 2012-02-29 09:42, Stephan Bergmann wrote:
On 02/28/2012 02:48 PM, Lubos Lunak wrote:
Speaking of the size at the call-site, I good part is the code
trying to
throw std::bad_alloc in case the allocation fails. That actually
looks rather
useless to me, for several reasons:
Disclaimer: http://www.peralex.com/disclaimer.html
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
