Re: [GiNaC-list] Memory leak in dynallocate for relational

9 Jan 2017

      Hi Thomas,

On 01/09/2017 04:49 PM, Thomas Luthe wrote:
...
valgrind reports a memory leak caused by dynallocate<GiNaC::relational,
const GiNaC::ex&, const GiNaC::ex&, GiNaC::relational::operators>
(basic.h:336). I have attached a minimal example as well as the
corresponding valgrind output I get. The executable was produced with
g++ 5.4 -O0 and GiNaC 1.7.1.
Repeated use of operators == or != for GiNaC::ex does indeed lead to a
noticeable increase of memory usage in applications, whereas
ex::is_equal does not have the same effect.
Thanks a lot for reporting this bug!

Indeed, some inadvertent changes have crept into 82df71852. I've
committed a patch.

All my best,
  -richy.
-- 
Richard B. Kreckel
<http://in.terlu.de/~kreckel/>