Hi Arie,
I recommand the following. First, lookup the smilint source code and refer to error handling code, then you can exclude the illegal MIB error. Next, use C++ exception or MFC exception, then you can handle unstable libsmi. Last, modify the source of libsmi. There would be nothing for it but to modify the source for meeting the personal need.
I wish your success!
----- Original Message ----- From: "Arie Trost" ariet@genesyslab.com To: "'Kang, Jeongwon'" hanule@3ic.co.kr Cc: libsmi@ibr.cs.tu-bs.de Sent: Tuesday, January 15, 2002 5:10 AM Subject: RE: [libsmi] memory leak; program terminates
Hi Kang,
Thanks for the tip, this did the trick.
I've noticed that exit(-1) statement in printError(). I would like my application to skip a MIB module that caused a failure and continue loading other MIBs. How can I handle this situation in my application (do some cleanup for a falty MIB and prepare for loading the next one)?
Thank you, Arie.
-- !! 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.