Re: why are we catching std::bad_alloc ?

Stephan Bergmann <sbergman -AT- redhat.com>

Tue, 08 Jan 2013 16:11:57 +0100

On 01/04/2013 08:53 AM, Noel Grandin wrote:

Why are we catching std::bad_alloc all over the place?

     git grep 'catch.*bad_alloc' | wc -l
     68

Surely we should just let it crash?
Or have a single handler for the whole process that at least attempts to
provide some debugging data?
At the moment, most of them just log something and then continues, which
strikes me as counter-productive.

Some of the catch blocks might be (somewhat hopeless) attempts at making

functions (typically those implementing UNO interface methods) adhere to

their dynamic exception specifications.

Stephan

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.