On 02/29/2012 08:57 AM, Noel Grandin wrote:
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.
But, as I argue, propagating to the call site is generally better and apparently hardly more expensive in practice.
Stephan _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
