Hello all,

I downloaded libsmi v 0.2.16 from "http://www.ibr.cs.tu-bs.de/projects/libsmi/" and compiled it under win32 using VC++6 using the makefile provided in the "win" subdir.

To find possible memory leaks I included:

#define _CRTDBG_MAP_ALLOC #include <stdlib.h> #include <crtdbg.h>

at the beginning and:

_CrtDumpMemoryLeaks(); // just before return 0; in main()

at the end of "smidump.c"

Secondly, I uncommented #DEBUG in the win\makefile and added /MLd (single-threaded debug)

DEBUG = -W3 -Zi -Od /Yd /MLd

Finally I ran smidump.exe on rfc1213-mib and this resulted in huge number of memory leaks:

Detected memory leaks! Dumping objects -> {2579} normal block at 0x0050E8C8, 5 bytes long. Data: <snmp > 73 6E 6D 70 00 {2563} normal block at 0x0050E268, 5 bytes long. Data: <snmp > 73 6E 6D 70 00 {2559} normal block at 0x0050E188, 8 bytes long. Data: <Counter > 43 6F 75 6E 74 65 72 00 {2555} normal block at 0x0050DFB8, 5 bytes long. Data: <snmp > 73 6E 6D 70 00 ... // lots more

I suspect that there is a leak for every single MIB object (not sure).

Is anyone aware of this ? This is pretty severe for applications which stay permanently in memory and have to compile SMI files on a regular basis.

Abhay Deshmukh Sr. Development Engineer BarcoNet Private Limited Tidel Park Module #0305 Taramani, Chennai 600 113. INDIA. Tel +91 44 2540601/02/03/04 ext 205 Fax +91 44 2540605 Mailto : abhayanil.deshmukh@barconet.com

-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.