#982 Dune::className has a memory leak
Metadata
| Property | Value |
|---|---|
| Reported by | Andreas Lauser (andreas.lauser@iws.uni-stuttgart.de) |
| Reported at | Nov 23, 2011 18:43 |
| Type | Bug Report |
| Version | 2.1 |
| Operating System | Unspecified / All |
| Last edited by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Last edited at | Nov 24, 2011 06:10 |
| Closed by | Oliver Sander (oliver.sander@tu-dresden.de) |
| Closed at | Nov 24, 2011 06:10 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment | Backported the original fix from revision 6402 to the 2.1 branch in commit 6531 |
Description
according to
http://gcc.gnu.org/onlinedocs/libstdc++/manual/ext_demangling.html
the string returned by __cxa_demangle must be freed which was not the case and lead to valgrind complaints.
The attached patch is for DUNE 2.1, but I doubt that dune/common/classname.hh was changed in the mean time, so it should apply to trunk as well. I would also like to ask whether this patch can be included in the DUNE 2.1 branch.