Libsmi May 2011

libsmi@ibr.cs.tu-bs.de

2 participants
4 discussions

smidump --format=smiv2 output contains some errors in compliance SYNTAX/WRITE-SYNTAX clauses.
by Jens Engel 06 Jun '13

06 Jun '13

Hello, I just stumbled over the following problem in libsmi 0.4.8 and development trunk-tip rev34557 (as of today). The problem resides in the SYNTAX/WRITE-SYNTAX clauses in COMPLIANCE statements. Instead of a "type" the invalid term "(null)" is present. AFFECTED-MIBS (at least): - BRIDGE-MIB - SNMP-VIEW-BASED-ACM-MIB - ... => grep "(null)" *-MIB EXAMPLE: smidump --format=smiv2 BRIDGE-MIB ... OBJECT dot1dStpPriority SYNTAX (null) (0 | 4096 | 8192 | 12288 | 16384 | 20480 | 24576 | 28672 | 32768 | 36864 | 40960 | 45056 | 49152 | 53248 | 57344 | 61440) ... OBJECT dot1dStpPortPriority SYNTAX (null) (0 | 16 | 32 | 48 | 64 | 80 | 96 | 112 | 128 | 144 | 160 | 176 | 192 | 208 | 224 | 240) BUT: Original BRIDGE-MIB that is distributed w/ libsmi contains: OBJECT dot1dStpPriority SYNTAX Integer32 (0 | 4096 | 8192 | 12288 | 16384 | 20480 | 24576 | 28672 | 32768 | 36864 | 40960 | 45056 | 49152 | 53248 | 57344 | 61440) ... OBJECT dot1dStpPortPriority SYNTAX Integer32 (0 | 16 | 32 | 48 | 64 | 80 | 96 | 112 | 128 | 144 | 160 | 176 | 192 | 208 | 224 | 240) smidump --format=smiv2 SNMP-VIEW-BASED-ACM-MIB ... OBJECT vacmViewTreeFamilyMask WRITE-SYNTAX (null) (SIZE(0)) ... SHOULD-BE (as in original MIB distributed with libsmi): ... OBJECT vacmViewTreeFamilyMask WRITE-SYNTAX OCTET STRING (SIZE(0)) I assume that smidump does not have the info (only a NULL pointer) and just dumps it as textual info. NOTE: "smidiff <ORIGINAL-MIB> <SMIDUMPED-MIB>" does not seem to show a difference (except warnings, ...). Ciao, Jens

3 2

Segfault when parsing invalid MIB
by Vincent Bernat 18 Jun '11

18 Jun '11

Hi! On my computer, smilint RMON2-MIB leads to a segfault because, I think, the rmon symbol is not known because of a missing MIB which leads to an incorrect tokenRing symbol. For example, with smiquery: MibNode: TOKEN-RING-RMON-MIB::tokenRing OID: 32395664.0 Declaration: <value-assignment> NodeKind: node I think that the bogus OID is related to the segfault which happens in checkObjects in the loop that should find the parent node which follows an invalid pointer. I have looked around the segfault but every data is corrupted in the core file. Even modulePtr is not correct at all. I have taken this very small MIB : INVALID-MIB DEFINITIONS ::= BEGIN IMPORTS rmon FROM NORFC-MIB; tokenRing OBJECT IDENTIFIER ::= { rmon 10 } END rmon is not solvable and tokenRing is not solvable too. This does not lead to a segfault, but I get bogus OID : Module: INVALID-MIB MibNode: INVALID-MIB::tokenRing OID: 23465424.0 Declaration: <value-assignment> NodeKind: node I have followed the parser step by step (smiparse()). At the exit of this function, parser.modulePtr is correct. The first object is rmon with OID 0 and the second object is tokenRing with OID 0.10. However, after freeNodeTree(), the second object OID becomes 0.0. I did not see any other change. If I comment freeNodeTree() and smiFree() and try again smiquery, I get: Module: INVALID-MIB MibNode: INVALID-MIB::tokenRing OID: 0.10 ParentNode: INVALID-MIB::rmon Declaration: <value-assignment> NodeKind: node Which seems correct. On the real MIB, I get: Module: RFC1155-SMI Module: TOKEN-RING-RMON-MIB MibNode: TOKEN-RING-RMON-MIB::tokenRing OID: 0.10 ParentNode: TOKEN-RING-RMON-MIB::rmon Declaration: <value-assignment> NodeKind: node Which is fine too. However, smilint still segfaults. I have tried to comment other occurrences of the same pattern with no luck. I am not sure to grasp the structures used by the parser but I believe that when there is no way to link a part of the tree, it is freed. Maybe, those nodes should be attached to some fake element in parser-smi.y instead of setting parentPtr to NULL? I have tried to attach them to modulePtr->firstObjectPtr without any luck. Maybe someone can point me in the right direction to get this right? -- GARLIC GUM IS NOT FUNNY GARLIC GUM IS NOT FUNNY GARLIC GUM IS NOT FUNNY -+- Bart Simpson on chalkboard in episode 7G13

1 2

Potential bug in forward nodes references (this time with no awful horizontal wrapping...)
by cedric arbogast 09 May '11

09 May '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, This is my first contact and mail with this mailing list, to summarize i'm a coder maintening a personnal home server using several GNU tools since the late 90's. I build LIBMSI-0.4.8 in a chroot jail (gcc 4.5.2/libc 2.13/binutils 2.21/make 3.82) with an athlon architecture on ext3 FS and, as root,got one failed test on tests/parser : [root@pompomgalli] mkdir libmsi-0.4.8_build && cd libmsi-0.4.8_build [root@pompomgalli] ../libsmi-0.4.8/configure --prefix=/usr checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes .... [root@pompomgalli] make .... make[2]: Leaving directory `/usr/src_app/libsmi-0.4.8_build' make[1]: Leaving directory `/usr/src_app/libsmi-0.4.8_build' [root@pompomgalli] make check ... PASS: smidump-orig-smiv2.test comparing `smidump -f smiv2 ../dumps/smiv2/SNMPv2-MIB' output with dumps/smiv2-smiv2/*. comparing `smidump -f smiv2 ../dumps/smiv2/IF-MIB' output with dumps/smiv2-smiv2/*. comparing `smidump -f smiv2 ../dumps/smiv2/MAU-MIB' output with dumps/smiv2-smiv2/*. comparing `smidump -f smiv2 ../dumps/smiv2/RMON2-MIB' output with dumps/smiv2-smiv2/*. PASS: smidump-smiv2-smiv2.test Checking LIBSMI-TEST-001-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-002-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-003-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-004-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-005-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-006-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-007-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-008-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-009-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-010-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-011-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-012-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-013-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-014-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-015-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-016-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-017-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-018-MIB. unexpected output. see parser.out directory. FAIL: parser.test checking smidiff results for *. /bin/diff: *.diff: No such file or directory PASS: smidiff.test ==================== 1 of 21 tests failed ==================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make: *** [check-recursive] Error 1 [root@pompomgalli] Therefore, i check one of the failed output : [root@pompomgalli] cat test/parser.out/LIBSMI-TEST-003-MIB.err [root@pompomgalli] cat test/parser.out/LIBSMI-TEST-003-MIB.expect LIBSMI-TEST-003-MIB:45: more than one MODULE-IDENTITY clause in SMIv2 MIB LIBSMI-TEST-003-MIB:45: MODULE-IDENTITY clause must be the first declaration in a module LIBSMI-TEST-003-MIB:53: revision not in reverse chronological order I then launch manually the LIBSMI-TEST-003-MIB test : [root@pompomgalli] SMIPATH=$SMIPATH:../libsmi-0.4.8/mibs/ietf:../libsmi-0.4.8/mibs:../libsmi-0.4.8/test/mibs tools/smilint -c/dev/null -l9 ../libsmi-0.4.8/test/mibs/LIBSMI-TEST-003-MIB 2>&1 Segmentation fault (core dumped) [root@pompomgalli] I have 'straced' the test but found nothing noticeable. As i am too lazy to launch gdb, i have first googling about related troubles regarding libsmi and found Vincent Bernat mail (http://www.ibr.cs.tu-bs.de/pipermail/libsmi/2010-August/001214.html). So, starting from his premises, i looked after the handling of module's nodes trees, and, to resume, seen that Vincent Bernat seems to be right when commenting the freeNodeTree and smiFree calls in loadModule (data.c). The nodes allocated for the module could have been referenced by the parser and used later in the parse process (case 344 in parser-smi.c), therefore they should not be freed at the end of the loadModule call but at the end of the parse process (imho). While i was investigate, i have also noticed that the checkObjects method in parser-smi.c does not handle the case of a malformed tree where a node could not have been linked to the root tree while searching possibly incorrect oidlen/oid values. I suggest theses two patchs to address that : --- ../libsmi-0.4.8/lib/parser-smi.c.orig 2008-04-18 14:58:11.000000000 +0200 +++ ../libsmi-0.4.8/lib/parser-smi.c 2011-05-08 16:33:24.000000000 +0200 @@ -954,6 +954,7 @@ nodePtr->parentPtr != thisParserPtr->pendingNodePtr && nodePtr->parentPtr != smiHandle->rootNodePtr && nodePtr != nodePtr->parentPtr && + nodePtr->parentPtr != NULL && i <= 128; nodePtr = nodePtr->parentPtr, i++); if ((objectPtr->export.name) && --- ../libsmi-0.4.8/lib/data.c.orig 2008-04-18 12:42:50.000000000 +0200 +++ ../libsmi-0.4.8/lib/data.c 2011-05-08 16:24:21.000000000 +0200 @@ -4737,8 +4737,9 @@ smiDepth++; parser.line = 1; smiparse((void *)&parser); - freeNodeTree(parser.pendingNodePtr); - smiFree(parser.pendingNodePtr); + // Nodes must NOT be freed here because forward references could be reached by imported modules ref + // freeNodeTree(parser.pendingNodePtr); + // smiFree(parser.pendingNodePtr); smiLeaveLexRecursion(); smiDepth--; fclose(parser.file); @@ -4780,6 +4781,9 @@ smiDepth++; parser.line = 1; smingparse((void *)&parser); + // Nodes must NOT be freed here because forward references could be reached by imported modules ref + // freeNodeTree(parser.pendingNodePtr); + // smiFree(parser.pendingNodePtr); freeNodeTree(parser.pendingNodePtr); smiFree(parser.pendingNodePtr); smingLeaveLexRecursion(); For parser-smi.c, it seems that quitting the loop when the node's parent is null is right regarding the goal to control that the tree does not exceed 128 nodes. Perhaps it could be useful to add an error message when this loop detects an 'unlinked' node. With theses patchs, the parser test gives the following results : [root@pompomgalli] make check ... PASS: smidump-smiv2-smiv2.test Checking LIBSMI-TEST-001-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-002-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-003-MIB. 3 errors/warnings, ok. Checking LIBSMI-TEST-004-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-005-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-006-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-007-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-008-MIB. 21 errors/warnings, ok. Checking LIBSMI-TEST-009-MIB. 23 errors/warnings, ok. Checking LIBSMI-TEST-010-MIB. 10 errors/warnings, ok. Checking LIBSMI-TEST-011-MIB. 3 errors/warnings, ok. Checking LIBSMI-TEST-012-MIB. 5 errors/warnings, ok. Checking LIBSMI-TEST-013-MIB. 14 errors/warnings, ok. Checking LIBSMI-TEST-014-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-015-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-016-MIB. 10 errors/warnings, ok. Checking LIBSMI-TEST-017-MIB. 12 errors/warnings, ok. Checking LIBSMI-TEST-018-MIB. 1 errors/warnings, ok. FAIL: parser.test checking smidiff results for *. /bin/diff: *.diff: No such file or directory PASS: smidiff.test ==================== 1 of 21 tests failed ==================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make: *** [check-recursive] Error 1 The LIBSMI-TEST-014-MIB is still failing with : [root@pompomgalli] diff -u test/parser.out/LIBSMI-TEST-014-MIB.err test/parser.out/LIBSMI-TEST-014-MIB.expect --- test/parser.out/LIBSMI-TEST-014-MIB.err 2011-05-08 17:50:51.000000000 +0200 +++ test/parser.out/LIBSMI-TEST-014-MIB.expect 2011-05-08 17:50:51.000000000 +0200 @@ -1,5 +1,7 @@ +LIBSMI-TEST-014-MIB:102: warning: index of row `barEntry' can exceed OID size limit by 1 subidentifier(s) +LIBSMI-TEST-014-MIB:186: warning: index of row `barImpliedEntry' can exceed OID size limit by 1 subidentifier(s) LIBSMI-TEST-014-MIB:251: index element `fooStringName' of row `fooStringEntry' must have a size restriction -LIBSMI-TEST-014-MIB:230: warning: index of row `fooStringEntry' can exceed OID size limit by 65421 subidentifier(s) +LIBSMI-TEST-014-MIB:230: warning: index of row `fooStringEntry' can exceed OID size limit by 65427 subidentifier(s) LIBSMI-TEST-014-MIB:294: index element `fooOidName' of row `fooOidEntry' should but cannot have a size restriction -LIBSMI-TEST-014-MIB:273: warning: index of row `fooOidEntry' can exceed OID size limit by 14 subidentifier(s) +LIBSMI-TEST-014-MIB:273: warning: index of row `fooOidEntry' can exceed OID size limit by 20 subidentifier(s) LIBSMI-TEST-014-MIB:309: warning: current group `fooOidBarGroup' is not referenced in this module Apparently, it is something else, i could investigate if it seems pertinent. I will maintain my chroot environment for few days, therefore i could make more tests if needed. Regards, Cedric. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3GxxUACgkQUPHT03kXaaZ9GgCghDhzqAyqwE7e2ZsV6C/ujzrR xooAnAtztelJGUsQOgvV3Y4Jp4AMXgH7 =a/54 -----END PGP SIGNATURE-----

2 1

Potential bug in forward nodes references
by cedric arbogast 08 May '11

08 May '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, This is my first contact and mail with this mailing list, to summarize i'm a coder maintening a personnal home server using several GNU tools since the late 90's. I build LIBMSI-0.4.8 in a chroot jail (gcc 4.5.2/libc 2.13/binutils 2.21/make 3.82) with an athlon architecture on ext3 FS and, as root, got one failed test on tests/parser : [root@pompomgalli] mkdir libmsi-0.4.8_build && cd libmsi-0.4.8_build [root@pompomgalli] ../libsmi-0.4.8/configure --prefix=/usr checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes .... [root@pompomgalli] make .... make[2]: Leaving directory `/usr/src_app/libsmi-0.4.8_build' make[1]: Leaving directory `/usr/src_app/libsmi-0.4.8_build' [root@pompomgalli] make check ... PASS: smidump-orig-smiv2.test comparing `smidump -f smiv2 ../dumps/smiv2/SNMPv2-MIB' output with dumps/smiv2-smiv2/*. comparing `smidump -f smiv2 ../dumps/smiv2/IF-MIB' output with dumps/smiv2-smiv2/*. comparing `smidump -f smiv2 ../dumps/smiv2/MAU-MIB' output with dumps/smiv2-smiv2/*. comparing `smidump -f smiv2 ../dumps/smiv2/RMON2-MIB' output with dumps/smiv2-smiv2/*. PASS: smidump-smiv2-smiv2.test Checking LIBSMI-TEST-001-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-002-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-003-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-004-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-005-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-006-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-007-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-008-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-009-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-010-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-011-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-012-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-013-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-014-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-015-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-016-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-017-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-018-MIB. unexpected output. see parser.out directory. FAIL: parser.test checking smidiff results for *. /bin/diff: *.diff: No such file or directory PASS: smidiff.test ==================== 1 of 21 tests failed ==================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make: *** [check-recursive] Error 1 [root@pompomgalli] Therefore, i check one of the failed output : [root@pompomgalli] cat test/parser.out/LIBSMI-TEST-003-MIB.err [root@pompomgalli] cat test/parser.out/LIBSMI-TEST-003-MIB.expect LIBSMI-TEST-003-MIB:45: more than one MODULE-IDENTITY clause in SMIv2 MIB LIBSMI-TEST-003-MIB:45: MODULE-IDENTITY clause must be the first declaration in a module LIBSMI-TEST-003-MIB:53: revision not in reverse chronological order I then launch manually the LIBSMI-TEST-003-MIB test : [root@pompomgalli] SMIPATH=$SMIPATH:../libsmi-0.4.8/mibs/ietf:../libsmi-0.4.8/mibs:../libsmi-0.4.8/test/mibs tools/smilint -c/dev/null -l9 ../libsmi-0.4.8/test/mibs/LIBSMI-TEST-003-MIB 2>&1 Segmentation fault (core dumped) [root@pompomgalli] I have 'straced' the test but found nothing noticeable. As i am too lazy to launch gdb, i have first googling about related troubles regarding libsmi and found Vincent Bernat mail (http://www.ibr.cs.tu-bs.de/pipermail/libsmi/2010-August/001214.html). So, starting from his premises, i looked after the handling of module's nodes trees, and, to resume, seen that Vincent Bernat seems to be right when commenting the freeNodeTree and smiFree calls in loadModule (data.c). The nodes allocated for the module could have been referenced by the parser and used later in the parse process (case 344 in parser-smi.c), therefore they should not be freed at the end of the loadModule call but at the end of the parse process (imho). While i was investigate, i have also noticed that the checkObjects method in parser-smi.c does not handle the case of a malformed tree where a node could not have been linked to the root tree while searching possibly incorrect oidlen/oid values. I suggest theses two patchs to address that : --- ../libsmi-0.4.8/lib/parser-smi.c.orig 2008-04-18 14:58:11.000000000 +0200 +++ ../libsmi-0.4.8/lib/parser-smi.c 2011-05-08 16:33:24.000000000 +0200 @@ -954,6 +954,7 @@ nodePtr->parentPtr != thisParserPtr->pendingNodePtr && nodePtr->parentPtr != smiHandle->rootNodePtr && nodePtr != nodePtr->parentPtr && + nodePtr->parentPtr != NULL && i <= 128; nodePtr = nodePtr->parentPtr, i++); if ((objectPtr->export.name) && --- ../libsmi-0.4.8/lib/data.c.orig 2008-04-18 12:42:50.000000000 +0200 +++ ../libsmi-0.4.8/lib/data.c 2011-05-08 16:24:21.000000000 +0200 @@ -4737,8 +4737,9 @@ smiDepth++; parser.line = 1; smiparse((void *)&parser); - freeNodeTree(parser.pendingNodePtr); - smiFree(parser.pendingNodePtr); + // Nodes must NOT be freed here because forward references could be reached by imported modules ref + // freeNodeTree(parser.pendingNodePtr); + // smiFree(parser.pendingNodePtr); smiLeaveLexRecursion(); smiDepth--; fclose(parser.file); @@ -4780,6 +4781,9 @@ smiDepth++; parser.line = 1; smingparse((void *)&parser); + // Nodes must NOT be freed here because forward references could be reached by imported modules ref + // freeNodeTree(parser.pendingNodePtr); + // smiFree(parser.pendingNodePtr); freeNodeTree(parser.pendingNodePtr); smiFree(parser.pendingNodePtr); smingLeaveLexRecursion(); For parser-smi.c, it seems that quitting the loop when the node's parent is null is right regarding the goal to control that the tree does not exceed 128 nodes. Perhaps it could be useful to add an error message when this loop detects an 'unlinked' node. With theses patchs, the parser test gives the following results : [root@pompomgalli] make check ... PASS: smidump-smiv2-smiv2.test Checking LIBSMI-TEST-001-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-002-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-003-MIB. 3 errors/warnings, ok. Checking LIBSMI-TEST-004-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-005-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-006-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-007-MIB. 1 errors/warnings, ok. Checking LIBSMI-TEST-008-MIB. 21 errors/warnings, ok. Checking LIBSMI-TEST-009-MIB. 23 errors/warnings, ok. Checking LIBSMI-TEST-010-MIB. 10 errors/warnings, ok. Checking LIBSMI-TEST-011-MIB. 3 errors/warnings, ok. Checking LIBSMI-TEST-012-MIB. 5 errors/warnings, ok. Checking LIBSMI-TEST-013-MIB. 14 errors/warnings, ok. Checking LIBSMI-TEST-014-MIB. unexpected output. see parser.out directory. Checking LIBSMI-TEST-015-MIB. 0 errors/warnings, ok. Checking LIBSMI-TEST-016-MIB. 10 errors/warnings, ok. Checking LIBSMI-TEST-017-MIB. 12 errors/warnings, ok. Checking LIBSMI-TEST-018-MIB. 1 errors/warnings, ok. FAIL: parser.test checking smidiff results for *. /bin/diff: *.diff: No such file or directory PASS: smidiff.test ==================== 1 of 21 tests failed ==================== make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/src_app/libsmi-0.4.8_build/test' make: *** [check-recursive] Error 1 The LIBSMI-TEST-014-MIB is still failing with : [root@pompomgalli] diff -u test/parser.out/LIBSMI-TEST-014-MIB.err test/parser.out/LIBSMI-TEST-014-MIB.expect --- test/parser.out/LIBSMI-TEST-014-MIB.err 2011-05-08 17:50:51.000000000 +0200 +++ test/parser.out/LIBSMI-TEST-014-MIB.expect 2011-05-08 17:50:51.000000000 +0200 @@ -1,5 +1,7 @@ +LIBSMI-TEST-014-MIB:102: warning: index of row `barEntry' can exceed OID size limit by 1 subidentifier(s) +LIBSMI-TEST-014-MIB:186: warning: index of row `barImpliedEntry' can exceed OID size limit by 1 subidentifier(s) LIBSMI-TEST-014-MIB:251: index element `fooStringName' of row `fooStringEntry' must have a size restriction -LIBSMI-TEST-014-MIB:230: warning: index of row `fooStringEntry' can exceed OID size limit by 65421 subidentifier(s) +LIBSMI-TEST-014-MIB:230: warning: index of row `fooStringEntry' can exceed OID size limit by 65427 subidentifier(s) LIBSMI-TEST-014-MIB:294: index element `fooOidName' of row `fooOidEntry' should but cannot have a size restriction -LIBSMI-TEST-014-MIB:273: warning: index of row `fooOidEntry' can exceed OID size limit by 14 subidentifier(s) +LIBSMI-TEST-014-MIB:273: warning: index of row `fooOidEntry' can exceed OID size limit by 20 subidentifier(s) LIBSMI-TEST-014-MIB:309: warning: current group `fooOidBarGroup' is not referenced in this module Apparently, it is something else, i could investigate if it seems pertinent. I will maintain my chroot environment for few days, therefore i could make more tests if needed. Regards, Cedric. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3GxD4ACgkQUPHT03kXaaaRkACgn8HDsceBfXD4e6CH2GGqwT7y TPQAoIyxL9n4F8V89YPsg6LHa+84k5Hr =G2QS -----END PGP SIGNATURE-----

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Libsmi May 2011