[iostreams][bug] Uncaught exception in destructor when using file_descriptor
https://svn.boost.org/trac/boost/ticket/2932 I hope it's appropriate to ping the list about this issue, which was reported 4 months ago and has not been fixed in 1.39.0 or on the trunk. If closing a file descriptor fails, file_descriptor::impl::~impl() (or file_descriptor_impl::~file_descriptor_impl() on the trunk) throws an exception. This has the potential to happen during stack unwinding, causing immediate std::terminate(). Since the fix appears to be a trivial addition of try { /*...*/ } catch (...) {} it'd be a shame if this wasn't fixed in 1.40.0. Cheers, Gareth ************************************************************************ The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only. This email and any response may be monitored by Sony to be in compliance with Sony's global policies and standards
I hope it's appropriate to ping the list about this issue, which was reported 4 months ago and has not been fixed in 1.39.0 or on the
I got no response to my last e-mail, and there has been no response on Trac. I'm not sure if Jonathan Turkanis is actively maintaining Boost.Iostreams? Although there are changes to the library on the trunk, there doesn't appear to be any real differences between Boost.Iostreams in 1.35.0 and the current release branch. How can we get this trivial patch applied soon? trunk.
If closing a file descriptor fails, file_descriptor::impl::~impl() (or file_descriptor_impl::~file_descriptor_impl() on the trunk) throws an exception. This has the potential to happen during stack unwinding, causing immediate std::terminate().
Since the fix appears to be a trivial addition of try { /*...*/ }
catch
(...) {} it'd be a shame if this wasn't fixed in 1.40.0.
Many thanks, Gareth ************************************************************************ The information contained in this message or any of its attachments may be confidential and is intended for the exclusive use of the addressee(s). Any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited without the express permission of the sender. The views expressed in this email are those of the individual and not necessarily those of Sony or Sony affiliated companies. Sony email is for business use only. This email and any response may be monitored by Sony to be in compliance with Sony's global policies and standards
Sylvester-Bradley, Gareth wrote:
I got no response to my last e-mail, and there has been no response on Trac.
I'm not sure if Jonathan Turkanis is actively maintaining Boost.Iostreams? Although there are changes to the library on the trunk, there doesn't appear to be any real differences between Boost.Iostreams in 1.35.0 and the current release branch.
I have no idea either.
How can we get this trivial patch applied soon?
I just looked at the ticket, and while it does appear "trivial", it doesn't appear to have an explicit patch attached to the ticket. My guess is that if there were an explicit tested patch (including a fix and a test case) attached to the ticket, that some boost developer would take up the mantle.
Since the fix appears to be a trivial addition of try { /*...*/ }
catch
(...) {} it'd be a shame if this wasn't fixed in 1.40.0.
participants (2)
-
eg -
Sylvester-Bradley, Gareth