How to make apache mempool work with valgrind?

View: New views
3 Messages — Rating Filter:   Alert me  

How to make apache mempool work with valgrind?

by sc1801 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I found that valgrind is quite useful after several days using it, and
as far as I know,
to make valgrind work well with apache mempool (APR Libaray), it should
make some change in mempool source code, My question is "is there
already some APR patches to use ? and if so, where can I get it. And if
not,is someone else interested in develop one with me?"



Re: How to make apache mempool work with valgrind?

by Davi Arnaut-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

sc1801 wrote:
> I found that valgrind is quite useful after several days using it, and
> as far as I know,
> to make valgrind work well with apache mempool (APR Libaray), it should
> make some change in mempool source code, My question is "is there
> already some APR patches to use ? and if so, where can I get it. And if
> not,is someone else interested in develop one with me?"
>

When APR is compiled mode, the memory allocated from pools are mostly
directly taken from malloc() and hence are checked by valgrind.
Otherwise it would be nice to have some valgrind instrumentation for
non-debug builds.

-- Davi


Re: How to make apache mempool work with valgrind?

by Davi Arnaut-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Davi Arnaut wrote:

> sc1801 wrote:
>> I found that valgrind is quite useful after several days using it, and
>> as far as I know,
>> to make valgrind work well with apache mempool (APR Libaray), it should
>> make some change in mempool source code, My question is "is there
>> already some APR patches to use ? and if so, where can I get it. And if
>> not,is someone else interested in develop one with me?"
>>
>
> When APR is compiled mode, the memory allocated from pools are mostly

typo: "When APR is compiled in debug mode, the .."

> directly taken from malloc() and hence are checked by valgrind.
> Otherwise it would be nice to have some valgrind instrumentation for
> non-debug builds.

-- Davi
LightInTheBox - Buy quality products at wholesale price