
Hello, I updated my SMIPATH to point to the ietf mibs. This solved the exception problem. Previously, it pointed to the path for the foocorp and footest modules (not the ietf mib base.)
I am still concerned about the exception.
Thank you.
Pamela
Pamela Heckmann wrote:
Hello, I am using libsmi0.3.1 on Windows NT compiling with VC 6.0. When I load our sample mib module, I get an exception in smiparse() function in the scope of the loadModule() routine.
The code: if ($14) { if (((objectPtr->typePtr->export.basetype == SMI_BASETYPE_OCTETSTRING) && ($14->basetype != SMI_BASETYPE_OCTETSTRING)) || ((objectPtr->typePtr->export.basetype == SMI_BASETYPE_OBJECTIDENTIFIER) && ($14->basetype != SMI_BASETYPE_OBJECTIDENTIFIER))) { smiPrintError(thisParserPtr, ERR_DEFVAL_SYNTAX); if ($14->basetype == SMI_BASETYPE_OBJECTIDENTIFIER) { smiFree($14->value.oid); } if (($14->basetype == SMI_BASETYPE_BITS) || ($14->basetype == SMI_BASETYPE_OCTETSTRING)) { smiFree($14->value.ptr); } smiFree($14); }
gets an exception because objectPtr->typePtr is NULL. I ran smilint.exe against fooTest.mib and it gets an exception also. I have included our sample mibs that I have been testing with. fooTest.mib imports fooCorp.mib.
Any help would be appreciated.
Pamela
-- Pamela Heckmann Icon Laboratories, Inc. Pam_Heckmann@icon-labs.com The grand essentials to happiness in this life are something to do, something to love and something to hope for. - Joseph Addison
Name: fooCorp.mib
fooCorp.mib Type: Notepad File (application/x-unknown-content-type-MIBfile) Encoding: base64
Name: fooTest.mib
fooTest.mib Type: Notepad File (application/x-unknown-content-type-MIBfile) Encoding: base64
-- Pamela Heckmann Icon Laboratories, Inc. Pam_Heckmann@icon-labs.com The grand essentials to happiness in this life are something to do, something to love and something to hope for. - Joseph Addison