- Libsmi - lists.ibr.cs.tu-bs.de

MIB Errors
by Evgheni Antropov 02 Oct '12

02 Oct '12

Hello everybody I have a couple of issue, according with my own MIB file. I can divide error on 4 section: 1) [4] {group-membership} warning: node `Location' must be contained in at least one conformance group 2) [5] {group-unref} warning: current group `DNSGroup' is not referenced in this module 3) [2] {parent-scalar} scalar's parent node must be simple node 4) [5] {row-name-table-name} warning: row identifier `MetersTableEntry' should have the same prefix as table identifier `MetersTable' I cannot show my MIB File, but will try to explain it structure. I have about 100 nodes. Several of them are unite in groups, another - not. All of them consist in 2 main groups, which make connection with module-identity. In short I have follow structure: MODULE-IDENTITY -> OBJECT IDENTIFIER (2 different objects) | | | |-------> OBJECT-TYPE (several nodes) | | | |-------> TABLE (with index and several nodes OBJECT-TYPE) | |-----------> OBJECT-TYPE (several nodes) | |-----------> OBJECT-GROUP (several group) | | |---------> OBJECT-TYPE (several nodes) 1 section of error I have before MIB modification with adding OBJECT-GROUP. After adding groups I have received 2 and 3 section of errors. 4 section error regard only with table implementation. I have found all section of this errors on http://www.icir.org/fenner/mibs/htmllint/ and have checked all errors on this page http://www.icir.org/fenner/mibs/libsmi-errors, but unfortunately have not found any correct explanation how to fix those errors, except this one http://www.icir.org/fenner/mibs/libsmi-errors/group-membership.html . I have tried to understand RFC, but without any success. Also I have tried to compile MIB with specific soft, like MG-SOFT <http://www.mg-soft.si/> and it show only 4 section of error. I need to know if those warnings/errors are critical and if they can be fixed and how. All errors show on http://www.simpleweb.org/ietf/mibs/validate/ and http://www.ibr.cs.tu-bs.de/bin/smitools.cgi with severity level 3,4,5 and 6. During creation my own MIB file I have used for example DISMAN-PING-MIB which has not any errors in those online checks. If it's needed I will send my MIB file for better understand the issue. Thank you in advance. I will be glad for any help. WBR, Evgheni.

2 10

Problem with findNodeByParentAndSubid()?
by Scott, Damien 24 May '12

24 May '12

I have been investigating a possible problem with the function findNodeByParentAndSubid() in LibSMI's data.c file (v0.4.8). This function makes a comparison with smiHandle->parserPtr->pendingPtr. However, as far as I can tell, the parserPtr member of smiHandle is only ever set to point to a local variable (see the smiInitData() and loadModule() functions). This is fine when the local variable is still in scope (i.e. when findNodeByParentAndSubid() is called from within either the smiInitData() or loadModule() functions). The problem is that findNodeByParentAndSubid() is also called from getNode(), which is itself called from smiGetNode(). I was hoping to be able to call smiGetNode() from any point in the code, after the smiInitData() and loadModule() had already completed. If parserPtr goes out of scope and is re-used then the result of the comparison in findNodeByParentAndSubid() is affected. If pendingNodePtr ever gets set to the same value as parentNodePtr then the 'for' loop is skipped and NULL is returned. My workaround for now has been to modify findNodeByParentAndSubid() so that the comparison with parserPtr->pendingNodePtr is only carried out during initialisation (when safely being called from the smiInitData() or loadModule() functions). I am not completely clear as to the purpose of the pendingNodePtr or the comparison made in findNodeByParentAndSubid(). If anyone with a better understanding of LibSMI could comment or investigate, I would be grateful for any assistance. Thanks Damien Scott

1 0

Build errors under Cygwin
by R. Diez 07 May '12

07 May '12

Hi all: The release version 0.4.8 of libsmi does not build under Cygwin, see the build log at the bottom. Something is probably not right with asnprintf and the like. I would guess that this is not specific to Cygwin, it's probably an issue when building against newlib. asnprintf is being detected in the system C library, but it's redeclared in lib/snprintf.h anyway. I tried the Subversion head too, but I'm getting the same build problems. By the way, I noticed that autogen.sh seems to trigger "configure", which I don't think it's a good idea, as I want to specify my own "configure" argument before polluting the source directory. File autogen.sh is rather large, nowadays the following will probably do: autoreconf --warnings=all I would also fix the many autoconf warnings that the above command produces. Regards, R. Diez ---------8<---------8<---------8<---------8<--------- $ ./configure --prefix=/cygdrive/c/Ruben/SoftLib/libsmi/libsmi-0.4.8-bin checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for additional required compiler flags... checking for strtoll... yes checking for strtoull... yes checking for strtoq... no checking for strtouq... no checking for timegm... yes checking for vsnprintf... yes checking for snprintf... yes checking for asprintf... yes checking for asnprintf... yes checking for vasprintf... yes checking for vasnprintf... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking pwd.h usability... yes checking pwd.h presence... yes checking for pwd.h... yes checking for unistd.h... (cached) yes checking regex.h usability... yes checking regex.h presence... yes checking for regex.h... yes checking for stdint.h... (cached) yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking for regexec in -lc... yes checking for path separator character... : checking for dir separator character... / checking for 64 bit types... long long/%lld, etc. checking for flex... /cygdrive/c/WinAVR-20100110/utils/bin/flex checking for bison... /cygdrive/c/WinAVR-20100110/utils/bin/bison checking for bash... /usr/bin/sh checking for sh... /usr/bin/sh checking for awk... /usr/bin/awk checking for wget... /cygdrive/c/WinAVR-20100110/utils/bin/wget checking for gdiff... no checking for diff... /usr/bin/diff checking for a BSD-compatible install... /usr/bin/install -c checking whether make sets $(MAKE)... (cached) yes checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking for a sed that does not truncate output... /usr/bin/sed checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... file_magic ^x86 archive import|^x86 DLL checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking the maximum length of command line arguments... 8192 checking command to parse /usr/bin/nm -B output from gcc object... ok checking for objdir... .libs checking for ar... ar checking for ranlib... ranlib checking for strip... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for g77 option to produce PIC... checking if g77 static flag -static works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate configure: creating ./config.status config.status: creating Makefile config.status: creating lib/Makefile config.status: creating tools/Makefile config.status: creating mibs/Makefile config.status: creating mibs/iana/Makefile config.status: creating mibs/ietf/Makefile config.status: creating mibs/irtf/Makefile config.status: creating mibs/tubs/Makefile config.status: creating mibs/site/Makefile config.status: creating pibs/Makefile config.status: creating pibs/ietf/Makefile config.status: creating pibs/tubs/Makefile config.status: creating pibs/site/Makefile config.status: creating test/Makefile config.status: creating test/mibs/Makefile config.status: creating test/smidiff/Makefile config.status: creating test/dumps/Makefile config.status: creating test/dumps/corba/Makefile config.status: creating test/dumps/imports/Makefile config.status: creating test/dumps/jax/Makefile config.status: creating test/dumps/netsnmp/Makefile config.status: creating test/dumps/mosy/Makefile config.status: creating test/dumps/orig-smiv2/Makefile config.status: creating test/dumps/smilint-smiv2/Makefile config.status: creating test/dumps/sming/Makefile config.status: creating test/dumps/smiv1/Makefile config.status: creating test/dumps/smiv2/Makefile config.status: creating test/dumps/smiv2-smiv2/Makefile config.status: creating test/dumps/tree/Makefile config.status: creating test/dumps/types/Makefile config.status: creating test/dumps/identifiers/Makefile config.status: creating test/dumps/metrics/Makefile config.status: creating test/dumps/xml/Makefile config.status: creating test/dumps/cm/Makefile config.status: creating test/dumps/python/Makefile config.status: creating test/dumps/yang/Makefile config.status: creating doc/Makefile config.status: creating lib/smi.h config.status: creating lib/libsmi.3 config.status: creating lib/smi_macro.3 config.status: creating lib/smi_module.3 config.status: creating lib/smi_node.3 config.status: creating lib/smi_type.3 config.status: creating lib/smi_config.3 config.status: creating lib/smi_render.3 config.status: creating lib/smi_util.3 config.status: creating lib/smi_class.3 config.status: creating lib/smi_attribute.3 config.status: creating lib/smi_event.3 config.status: creating lib/smi_identity.3 config.status: creating tools/smistrip config.status: creating tools/smicache config.status: creating tools/smiquery.1 config.status: creating tools/smilint.1 config.status: creating tools/smidump.1 config.status: creating tools/smidiff.1 config.status: creating tools/smistrip.1 config.status: creating tools/smicache.1 config.status: creating tools/smixlate.1 config.status: creating tools/mib2svg.cgi config.status: creating test/parser.test config.status: creating test/smidump-corba.test config.status: creating test/smidump-jax.test config.status: creating test/smidump-netsnmp.test config.status: creating test/smidump-imports.test config.status: creating test/smidump-mosy.test config.status: creating test/smidump-orig-smiv2.test config.status: creating test/smidump-sming.test config.status: creating test/smidump-yang.test config.status: creating test/smidump-smiv1.test config.status: creating test/smidump-smiv2-smiv2.test config.status: creating test/smidump-smiv2.test config.status: creating test/smidump-tree.test config.status: creating test/smidump-types.test config.status: creating test/smidump-identifiers.test config.status: creating test/smidump-metrics.test config.status: creating test/smidump-xml.test config.status: creating test/smidump-cm.test config.status: creating test/smidump-python.test config.status: creating test/smilint-smiv2.test config.status: creating test/smidiff.test config.status: creating libsmi.pc config.status: creating win/config.h config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing default commands ---------8<---------8<---------8<---------8<--------- $ make make all-recursive make[1]: Entering directory `/cygdrive/c/Ruben/SoftLib/libsmi/libsmi-0.4.8' Making all in lib make[2]: Entering directory `/cygdrive/c/Ruben/SoftLib/libsmi/libsmi-0.4.8/lib' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT data.lo -MD -MP -MF .deps/data.Tpo -c -o data.lo data.c gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT data.lo -MD -MP -MF .deps/data.Tpo -c data.c -DPIC -o .libs/data.o gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT data.lo -MD -MP -MF .deps/data.Tpo -c data.c -o data.o >/dev/null 2>&1 mv -f .deps/data.Tpo .deps/data.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT check.lo -MD -MP -MF .deps/check.Tpo -c -o check.lo check.c gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT check.lo -MD -MP -MF .deps/check.Tpo -c check.c -DPIC -o .libs/check.o gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT check.lo -MD -MP -MF .deps/check.Tpo -c check.c -o check.o >/dev/null 2>&1 mv -f .deps/check.Tpo .deps/check.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT error.lo -MD -MP -MF .deps/error.Tpo -c -o error.lo error.c gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT error.lo -MD -MP -MF .deps/error.Tpo -c error.c -DPIC -o .libs/error.o gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT error.lo -MD -MP -MF .deps/error.Tpo -c error.c -o error.o >/dev/null 2>&1 mv -f .deps/error.Tpo .deps/error.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT util.lo -MD -MP -MF .deps/util.Tpo -c -o util.lo util.c gcc -DHAVE_CONFIG_H -I. -I.. -g -O2 -MT util.lo -MD -MP -MF .deps/util.Tpo -c util.c -DPIC -o .libs/util.o In file included from util.c:23:0: snprintf.h:50:12: error: conflicting types for 'asnprintf' /usr/include/stdio.h:246:8: note: previous declaration of 'asnprintf' was here snprintf.h:54:12: error: conflicting types for 'vasnprintf' /usr/include/stdio.h:276:8: note: previous declaration of 'vasnprintf' was here Makefile:380: recipe for target `util.lo' failed make[2]: *** [util.lo] Error 1 make[2]: Leaving directory `/cygdrive/c/Ruben/SoftLib/libsmi/libsmi-0.4.8/lib' Makefile:347: recipe for target `all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/cygdrive/c/Ruben/SoftLib/libsmi/libsmi-0.4.8' Makefile:239: recipe for target `all' failed make: *** [all] Error 2

2 1

Re: [libsmi] hey
by Samer Vazdekis 07 May '12

07 May '12

hey dont waste anymore time http://www.cnbc119.com

1 0

crash on pasing a list of mib files
by Strauhs, Gerhard 15 Feb '12

15 Feb '12

Hi, On parsing a list of mib files I encounter a crash when the file list is sorted before it is passed to the parser. I tracked the problem down to line 47xx of data.c. The call to the parser smiparse((void *)&parser); (shortly after #ifdef BACKEND_SMI) causes the crash. So to me it seems that this is some bug in the parser. However, the crash does not occur if the list is passed unsorted to the parser plus it only occurs on certain win systems. Thx fo any help. Gerhard Strauhs

1 0

Lost patch: parse all our mibs (fwd)
by Marcin Cieslak 12 Jan '12

12 Jan '12

did you mean this? //Marcin ---------- Forwarded message ---------- Date: Fri, 6 Jan 2012 23:40:26 From: Koen Van Hoof <koen.van_hoof(a)alcatel-lucent.com> To: "libsmi(a)ibr.cs.tu-bs.de" <libsmi(a)ibr.cs.tu-bs.de> Subject: [libsmi] parse all our mibs Hi, In order to be able to parse all our mibs, I have made some changes to libsmi. Here are my proposed changes. (See attached patches). 1) I have added SMI_ACCESS_WRITE_ONLY, because in SMIv1 this is also a valid access. 2) I have added SMI_BASETYPE_CHOICE. If the CHOICE type was SMI_BASETYPE_UNKNOWN, an import of that type caused a failure. 3) For the enum values of SMI_BASETYPE_ENUM, also the lists of the parent types are checked. 4) In SMIv1 'INTEGER(0..4294967295)' is vallid. In order to be able to parse this, a selection between SMI_BASETYPE_INTEGER32, SMI_BASETYPE_UNSIGNED64 and SMI_BASETYPE_UNSIGNED32 is made, based on the range of the integerSubType. 5) For SMIv1, the status 'mandatory', 'deprecated', 'obsolete' and 'optional' are parsed, and set to SMI_STATUS_MANDATORY, SMI_STATUS_DEPRECATED, SMI_STATUS_OBSOLETE and SMI_STATUS_OPTIONAL. 6) I have changed the check '(a->value.unsigned32> 1)&& (a->value.unsigned32-1> 2147483647))' into '(a->value.unsigned32>= 0x80000000u)'. This does not give any overflow, because it's an unsigned comparison (Notice the 'u' at the end of 0x80000000u. 7) In the last if statement, the result of compareValues was wrong, the parameters of the subtraction had to be switched. I have tested this with 'smi_dump -f xml' and the output is much better now. I hope my changes can contribute. :-) Koen Van Hoof -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust !! your settings, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de> !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/libsmi.

2 1

lost patch
by Juergen Schoenwaelder 11 Jan '12

11 Jan '12

Hi, a few days ago someone submitted a longer patch to me personally and I might have accidentally lost the message. If you submitted a patch recently, please resubmit. Sorry for the inconvenience. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/>

1 0

parse all our mibs
by Koen Van Hoof 07 Jan '12

07 Jan '12

Hi, In order to be able to parse all our mibs, I have made some changes to libsmi. Here are my proposed changes. (See attached patches). 1) I have added SMI_ACCESS_WRITE_ONLY, because in SMIv1 this is also a valid access. 2) I have added SMI_BASETYPE_CHOICE. If the CHOICE type was SMI_BASETYPE_UNKNOWN, an import of that type caused a failure. 3) For the enum values of SMI_BASETYPE_ENUM, also the lists of the parent types are checked. 4) In SMIv1 'INTEGER(0..4294967295)' is vallid. In order to be able to parse this, a selection between SMI_BASETYPE_INTEGER32, SMI_BASETYPE_UNSIGNED64 and SMI_BASETYPE_UNSIGNED32 is made, based on the range of the integerSubType. 5) For SMIv1, the status 'mandatory', 'deprecated', 'obsolete' and 'optional' are parsed, and set to SMI_STATUS_MANDATORY, SMI_STATUS_DEPRECATED, SMI_STATUS_OBSOLETE and SMI_STATUS_OPTIONAL. 6) I have changed the check '(a->value.unsigned32> 1)&& (a->value.unsigned32-1> 2147483647))' into '(a->value.unsigned32>= 0x80000000u)'. This does not give any overflow, because it's an unsigned comparison (Notice the 'u' at the end of 0x80000000u. 7) In the last if statement, the result of compareValues was wrong, the parameters of the subtraction had to be switched. I have tested this with 'smi_dump -f xml' and the output is much better now. I hope my changes can contribute. :-) Koen Van Hoof

1 0

Re: [libsmi] smilint and AUGMENTS
by Robert G Cole 04 Nov '11

04 Nov '11

I am having difficulty getting this MIB module to pass smilint. The issue relates to the use of AUGMENTS. If I do not IMPORT objects from RMON2, then I get severity [1] errors, but if I use IMPORT then I get the following severity [3] errors. Any advise to correct or is this an smilint issue? I have attached the draft MIB module. Thanks, Bob Cole > --------------------------------------- > > smilint returns: > > " > rgc@chapman:~/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02$ smilint -m > -s -l 6 -i > namelength-32 /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:523: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlObjects' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:524: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlBucketsRequested' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:525: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlBucketsGranted' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:529: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlInterval' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:532: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlOwner' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:534: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryControlStatus' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:543: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryObjectVariable' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:547: [3] {compliance-member-not-local} OBJECTS or NOTIFICATIONS member `usrHistoryObjectSampleType' is not defined in this module > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:307: [5] {index-element-accessible} warning: index element `reportSampledReportIndex' of row `reportSampledEntry' should be not-accessible in SMIv2 MIB > /home/rgc/IETF/MANET/REPORT-MIB/ietf-manet-report-mib-02/REPORT-SAMPLED-MIB:459: [5] {notification-not-reversible} warning: notification `reportSampledNewDataReport' is not reverse mappable > " > > Can't seem to get rid of the level [3] complaints. Basically, i can't > seem to use AUGMENTS without IMPORTS objects from RMON3, but then it > complains that these are not defined within this module. > > I have attached .xml and .txt.

3 4

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