Juergen Schoenwaelder wrote:
In general, I started to cleanup the SNMP engine code so that it becomes cleaner and a well defined library. This is not finished, but things are slowly moving forward.
It is very nice to hear that scli is still being developed.
Since the interface for the scli modes did not change much, it should be easy to integrate stuff into the current code base which was written against the current public version.
[The real reason why I did not release for some months now is that there is a nasty bug somewhere in the SNMP retransmission code where freed memory is used which I have not tracked down yet.]
Maybe valgrind may be of some use here? (http://www.tldp.org/HOWTO/Valgrind-HOWTO/ && http://valgrind.kde.org/)
<QUOTE> Valgrind is a system for debugging and profiling x86-Linux programs. Valgrind is capable of detection of many memory management and threading bugs, namely: - use of uninitialised memory - reading or writing memory after it has been free()d - reading or writing off the end of malloc()d blocks - reading or writing inappropriate areas on the stack - memory leaks - passing of uninitialised and/or unaddressible memory to system calls - mismatched use of malloc/new/new[] vs. free/delete/delete[] </QUOTE>
/js
MfG, Kurt Pfeifle
----------------------------------------------------------------- Co-Organizer of the KDE Community World Summit 2004 ("aKademy") http://conference2004.kde.org/ ------------ pfeifle@kde.org mobile:+49-172-715.7017 ------------ office:+49-711-4017-5677 -----------------------------------------------------------------