memory leak in res_nsend()

[Antony Dovgal]

On 24.10.2005 21:14, Daniel Jacobowitz wrote:
> On Mon, Oct 24, 2005 at 02:28:03PM +0400, Antony Dovgal wrote:
>> But res_nclose() doesn't free those segments.
>> That's what I've found in res_thread_freeres () function 
>> (resolv/res_init.c):
> 
> Well, when you're running under valgrind, the freeres functions are
> supposed to be called - for exactly this reason. 

Could you please elaborate: why should valgrind call something?
*I'm* calling res_nsend() and I suppose valgrind shouldn't call anything to free resources allocated by the user function calls.
Am I wrong?

> If it calls
> __libc_freeres but not __libc_thread_freeres, maybe you shold report
> this as a valgrind bug.


-- 
Wbr, 
Antony Dovgal