Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


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



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.