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

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-path-tp4661600p4661604.html

To start a new topic under Boost - Users, email [hidden email]
To unsubscribe from Boost, click here.
NAML

View this message in context: Re: Memory leak in boost::filesystems::parent_path()?
Sent from the Boost - Users mailing list archive at Nabble.com.