How are you getting leaks to show up?
I get piles of leaks in the cxx tests on eno, but none on sage.math.
Bill.
2009/1/10 Bill Hart :
> Hmm, not for me. I typed:
>
> valgrind --leak-check=full --show-reachable=yes ./t-locale
>
> It says no leaks are possible.
>
> Bill.
>
> 2009/1/10 mabshoff :
Hmm, not for me. I typed:
valgrind --leak-check=full --show-reachable=yes ./t-locale
It says no leaks are possible.
Bill.
2009/1/10 mabshoff :
>
>
>
> Bill Hart wrote:
>> Oh, probably standard locale is not available on that machine, so the
>> conditional compilation prevents the leak from sho
Bill Hart wrote:
> Oh, probably standard locale is not available on that machine, so the
> conditional compilation prevents the leak from showing up.
>
> Looks like I'll need access to a machine on which the leak occurs (and
> which has valgrind) in order to fix that one.
Ok, the problem shows
Oh, probably standard locale is not available on that machine, so the
conditional compilation prevents the leak from showing up.
Looks like I'll need access to a machine on which the leak occurs (and
which has valgrind) in order to fix that one.
Bill.
2009/1/10 Bill Hart :
> Hmm, when I valgrin
On Jan 10, 10:32 am, "Bill Hart" wrote:
> Hmm, when I valgrind t-locale on sage.math, no leaks show up. What am
> I doing wrong?
How exactly, i.e. with what parameters, are you calling valgrind?
> Bill.
Cheers,
Michael
--~--~-~--~~~---~--~~
You received this
Hmm, when I valgrind t-locale on sage.math, no leaks show up. What am
I doing wrong?
Bill.
2009/1/10 Bill Hart :
> Oh wait, C++ doesn't clean up automatically. The new needs to have a
> corresponding delete!!
>
> Bill.
>
> 2009/1/10 Bill Hart :
>> Sorry, that should say:
>>
>> "whose constructor
Oh wait, C++ doesn't clean up automatically. The new needs to have a
corresponding delete!!
Bill.
2009/1/10 Bill Hart :
> Sorry, that should say:
>
> "whose constructor is:
>
> explicit numpunct(
> size_t _Refs = 0
> );"
>
> Bill.
>
> 2009/1/10 Bill Hart :
>>
>> I've been taking a look at the m
Sorry, that should say:
"whose constructor is:
explicit numpunct(
size_t _Refs = 0
);"
Bill.
2009/1/10 Bill Hart :
>
> I've been taking a look at the memory leak in t-locale. According to
> the valgrind log there is a leak due to operator new(unsigned long) in
> set_point when called from ch
