Subject: memleak

memleak

From: Bram Matthys (Syzop) <syzop_at_vulnscan.org>
Date: 2005-11-17

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Figured I would let you dev guys know of this also (c-ares 1.3.0):

3713 bytes in 143 blocks are definitely lost in loss record 37 of 48
   at 0x1B90459D: malloc (vg_replace_malloc.c:130)
   by 0x80AAE9E: ares_expand_name (ares_expand_name.c:71)
   by 0x80AB697: ares_parse_ptr_reply (ares_parse_ptr_reply.c:77)
   by 0x80A8B25: addr_callback (ares_gethostbyaddr.c:161)
   by 0x80ACBA7: qcallback (ares_query.c:111)
   by 0x80A83A1: end_query (ares_process.c:693)
   by 0x80A7B49: process_answer (ares_process.c:373)
   by 0x80A790E: read_udp_packets (ares_process.c:287)
   by 0x80A7357: ares_process (ares_process.c:92)
   by 0x8057598: read_message (s_bsd.c:1786)
   by 0x8065AD8: main (ircd.c:1539)

Just in case you are not familiar with valgrind: 'definitely lost' means
a block of memory was never freed, and there are no pointers anywhere to
it (nor to anything inside the memory block).

I'm afraid I don't know what exact dns reply/replies trigger this (I'm
using a brute forcer), so it could well be quite hard to hunt down.

        Bram.

- --
Bram Matthys
Software developer/IT consultant syzop@vulnscan.org
PGP key: www.vulnscan.org/pubkey.asc
PGP fp: 8DD4 437E 9BA8 09AA 0A8D 1811 E1C3 D65F E6ED 2AA2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFDe8ZF4cPWX+btKqIRAjOYAKDuTuuTqjAV86Gyfa6QFeHJ6YhyTQCfcOj/
0RNA9EEACW9WyLgsuUUTa0E=
=IvGR
-----END PGP SIGNATURE-----
Received on Thu Nov 17 00:55:28 2005