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


I would expect that filters should be validating their inputs.
By the time that we get a bad_alloc, it's too late to recover properly.
Unless we're talking about someday running filters in a separate process, and then validating the document they generate, in which case the main process would remain safe.

On 2012-02-29 15:48, Eike Rathke wrote:
Hi Stephan,

On Wednesday, 2012-02-29 08:42:35 +0100, Stephan Bergmann wrote:

However, there are also situations where bad input (malicious or
otherwise) would cause an application to request excessive amounts
of memory to do a single task (e.g., open a document), and at least
in theory the application should be able to cope with such
externally-induced OOM conditions, by abandoning the bad operation,
cleaning up after it, telling the user the operation failed, and
carrying on.
I think catching std::bad_alloc and returning an error should be
possible in most filter code based on SfxObjectShell / SfxMedium.

   Eike



_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice

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.