Numerous memory leaks are patched in radius accounting proxy.
PS: It could be nice if developers before commiting something into cvs check code against memory leaks. It is quite simple: ./configure with-malloc=check, compile, run in test enviroment. Stop. Now, if in log files you see:
2003-10-08 13:23:54 [0] DEBUG: Current allocations: 0 areas, 0 bytes
then everything is Ok, but if you see something like:
2003-10-08 11:40:57 [0] DEBUG: Area 0x8271768, size 16, max_size 16 2003-10-08 11:40:57 [0] DEBUG: Allocated by udp_recvfrom() at gwlib/socket.c:733 2003-10-08 11:40:57 [0] DEBUG: Claimed by udp_recvfrom() at gwlib/socket.c:733 2003-10-08 11:40:57 [0] DEBUG: Contents of area (first 16 bytes): 2003-10-08 11:40:57 [0] DEBUG: 48 a2 26 08 10 00 00 00 11 00 00 00 00 00 00 00
2003-10-08 11:40:57 [0] DEBUG: Area 0x8271d18, size 16, max_size 16
2003-10-08 11:40:57 [0] DEBUG: Allocated by radius_attr_pack() at radius/radius_pdu.c:156
2003-10-08 11:40:57 [0] DEBUG: Claimed by radius_attr_pack() at radius/radius_pdu.c:156
2003-10-08 11:40:57 [0] DEBUG: Contents of area (first 16 bytes):
2003-10-08 11:40:57 [0] DEBUG: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2003-10-08 11:59:25 [0] DEBUG: Area 0x82d12d8, size 16, max_size 16
2003-10-08 11:59:25 [0] DEBUG: Allocated by update_tables() at radius/radius_acct.c:84
2003-10-08 11:59:25 [0] DEBUG: Claimed by update_tables() at radius/radius_acct.c:84
2003-10-08 11:59:25 [0] DEBUG: Contents of area (first 16 bytes):
2003-10-08 11:59:25 [0] DEBUG: e8 a7 2d 08 0d 00 00 00 0e 00 00 00 00 00 00 00
Then something is wrong and memory leaks are exists.
-- Vjacheslav Chekushin mailto:[EMAIL PROTECTED] Latvian Mobile Phone Company http://www.lmt.lv
radius_acct.patch.gz
Description: GNU Zip compressed data
