You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2008/01/02 22:28:33 UTC
[jira] Updated: (STDCXX-577) purify reports leaked memory in stocks
example
[ https://issues.apache.org/jira/browse/STDCXX-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-577:
--------------------------------
Attachment: stocks-valgrind.log
Btw., I get the attached leaks from valgrind on Linux (11S) even after applying the patch. Is Purify output clean in this build type?
> purify reports leaked memory in stocks example
> -----------------------------------------------
>
> Key: STDCXX-577
> URL: https://issues.apache.org/jira/browse/STDCXX-577
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Examples
> Affects Versions: 4.2.0
> Reporter: Travis Vitek
> Assignee: Travis Vitek
> Fix For: 4.2.1
>
> Attachments: stdcxx-577.patch, stocks-valgrind.log, stocks.log
>
>
> It is pretty obvious from looking at the source that memory is being leaked. The destructor for StockXchange doesn't deallocate memory allocated in StockXchange::add(), and the sl_pairs allocated in main are never deallocated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.