Otto Moerbeek wrote:
> yeah, MALLOC_STATS is not well maintained...
What's the relation between the MALLOC_STATS code currently in -stable,
and the code in your mdump [0] project? Are you experimenting with
different approaches?
BTW, thanks for your work on this.
0:
Omar Polo wrote:
> not tried, but compiles :)
Your patch made it compile for me too. With that change I was able to
run through the steps in https://www.drijf.net/malloc/ and detect memory
leaks! Thank you.
What's the process to get your change applied to -current? Should it be
submitted to the
Omar Polo wrote:
> There's a built-in mechanisms to check for memory leaks:
>
> https://www.drijf.net/malloc/
>
> don't know if it still applies, I tried only once and was like a couple
> of years ago (if not more).
Thanks for the tip, Omar. I just tried compiling malloc.c with
On Fri, Jul 23, 2021 at 11:54:38AM -0500, Joe Nelson wrote:
> Otto Moerbeek wrote:
> > yeah, MALLOC_STATS is not well maintained...
>
> What's the relation between the MALLOC_STATS code currently in -stable,
> and the code in your mdump [0] project? Are you experimenting with
> different
I'll take care.
Joe Nelson schreef op 23 juli 2021 18:36:04 CEST:
>Omar Polo wrote:
>> not tried, but compiles :)
>
>Your patch made it compile for me too. With that change I was able to
>run through the steps in https://www.drijf.net/malloc/ and detect
>memory
>leaks! Thank you.
>
>What's the
On Fri, Jul 23, 2021 at 06:02:08PM +0200, Omar Polo wrote:
>
> Joe Nelson writes:
>
> > Omar Polo wrote:
> >> There's a built-in mechanisms to check for memory leaks:
> >>
> >>https://www.drijf.net/malloc/
> >>
> >> don't know if it still applies, I tried only once and was like a couple
Joe Nelson writes:
> Omar Polo wrote:
>> There's a built-in mechanisms to check for memory leaks:
>>
>> https://www.drijf.net/malloc/
>>
>> don't know if it still applies, I tried only once and was like a couple
>> of years ago (if not more).
>
> Thanks for the tip, Omar. I just tried
7 matches
Mail list logo
