Memory leak in boost::filesystems::parent_path()?
Hi,
The following minimal program (only 7 lines) causes valgrind to report 2
errors, in line6:
Some somebody point me to why it is wrong?
a.cpp:
1 #include
On 23 Apr 2014 at 4:15, B.W.H. van Beest wrote:
The following minimal program (only 7 lines) causes valgrind to report 2 errors, in line6:
Some somebody point me to why it is wrong?
Both are bugs in libstdc++. They've been there for years. Should be fixed now in upstream, so upgrade your OS. Niall -- Currently unemployed and looking for work in Ireland. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
Thanks for the answer. You say 'should be fixed by now'. But I have a recent OS, openSuSe 13.1, regularly updated. version of libstdc== is: 4.8.1. (from: ) chopin:~ # rpm -q -a | grep libstdc++ libstdc++6-32bit-4.8.1_20130909-3.2.1.x86_64 libstdc++6-4.8.1_20130909-3.2.1.x86_64 libstdc++-devel-4.8-2.1.2.x86_64 libstdc++48-devel-4.8.1_20130909-3.2.1.x86_64 Do you know if the bug actually has been fixed? Kind Regards, Bertwim On 04/23/2014 11:52 AM, Niall Douglas [via Boost] wrote:
On 23 Apr 2014 at 4:15, B.W.H. van Beest wrote:
The following minimal program (only 7 lines) causes valgrind to report 2 errors, in line6:
Some somebody point me to why it is wrong?
Both are bugs in libstdc++. They've been there for years. Should be fixed now in upstream, so upgrade your OS.
Niall -- Currently unemployed and looking for work in Ireland. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
_______________________________________________ Boost-users mailing list [hidden email] http://lists.boost.org/mailman/listinfo.cgi/boost-users
*SMime.p7s* (8K) Download Attachment http://boost.2283326.n4.nabble.com/attachment/4661604/0/SMime.p7s
------------------------------------------------------------------------ If you reply to this email, your message will be added to the discussion below: http://boost.2283326.n4.nabble.com/Memory-leak-in-boost-filesystems-parent-p...
To start a new topic under Boost - Users, email ml-node+s2283326n2553780h57@n4.nabble.com To unsubscribe from Boost, click here http://boost.2283326.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2553779&code=Ynd2YkB4czRhbGwubmx8MjU1Mzc3OXwtNjM4MDQ0NjQ5. NAML http://boost.2283326.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
-- View this message in context: http://boost.2283326.n4.nabble.com/Memory-leak-in-boost-filesystems-parent-p... Sent from the Boost - Users mailing list archive at Nabble.com.
On 23 Apr 2014 at 9:24, Bertwim van Beest wrote:
You say 'should be fixed by now'. But I have a recent OS, openSuSe 13.1, regularly updated. version of libstdc== is: 4.8.1.
Do you know if the bug actually has been fixed?
I had understood it's fixed in trunk. Might have been backported to 4.9. I'd just add the relevant reports to a default suppressions file for the system and never worry about them again. Unfortunately, there is also undefined behaviour in libstdc++ which triggers a clang undefined behaviour sanitiser report every program run which cannot be easily suppressed, but is also apparently fixed in 4.9 - until then you have to use sed to filter the reports so the CI reports green :( Niall -- Currently unemployed and looking for work in Ireland. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/
Ok. Thanks for explaining the situation. Kind Regards, Bertwim On 04/24/2014 01:06 PM, Niall Douglas wrote:
On 23 Apr 2014 at 9:24, Bertwim van Beest wrote:
You say 'should be fixed by now'. But I have a recent OS, openSuSe 13.1, regularly updated. version of libstdc== is: 4.8.1.
Do you know if the bug actually has been fixed? I had understood it's fixed in trunk. Might have been backported to 4.9.
I'd just add the relevant reports to a default suppressions file for the system and never worry about them again. Unfortunately, there is also undefined behaviour in libstdc++ which triggers a clang undefined behaviour sanitiser report every program run which cannot be easily suppressed, but is also apparently fixed in 4.9 - until then you have to use sed to filter the reports so the CI reports green :(
Niall
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (3)
-
B.W.H. van Beest -
Bertwim van Beest
-
Niall Douglas