Libsmi April 2005

libsmi@ibr.cs.tu-bs.de

3 participants
4 discussions

Failing build from subversion repository
by Keith Dart 13 Dec '05

13 Dec '05

I obtained a subversion copy of libsmi, and try to build it (on two machines), I get the following: gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -MT parser-smi.lo -MD -MP -MF .deps/parser-smi.Tpo -c parser-smi.c -o parser-smi.o >/dev/null 2>&1 make[2]: *** No rule to make target `parser-smi.tab.h', needed by `scanner-smi.c'. Stop. make[2]: Leaving directory `/u01/home/kdart/src/libsmi/trunk/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/u01/home/kdart/src/libsmi/trunk' make: *** [all] Error 2 But I have flex and bison: 403 !$ bison --version bison (GNU Bison) 1.875 404 $ flex --version flex version 2.5.4 It looks like the Makefile does not include a rule for this, after all. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Keith Dart <kdart(a)kdart.com> public key: ID: F3D288E4 =====================================================================

2 1

Libsmi 0.4.3 memory fault (Linux/gcc)
by Allen McIntosh 03 May '05

03 May '05

The libsmi parser memory faults when parsing mibs/ietf/DOT12-RPTR-MIB. Repeat by running smilint mibs/ietf/DOT12-RPTR-MIB after installing libsmi. This happened to me under RedHat 9 (gcc 3.2.2/x86) and RedHat 7.3 (gcc 2.96/x86). The parser usually runs off the rails thus: $ gdb /usr/local/bin/smilint [stuff omitted] (gdb) run mibs/ietf/DOT12-RPTR-MIB Starting program: /usr/local/bin/smilint mibs/ietf/DOT12-RPTR-MIB mibs/ietf/DOT12-RPTR-MIB:36: revision for last update is missing mibs/ietf/DOT12-RPTR-MIB:151: warning: use Integer32 instead of INTEGER in SMIv2 Program received signal SIGSEGV, Segmentation fault. 0x40037b15 in checkObjects (parserPtr=0xbffff5f0, modulePtr=0x80559a0) at parser-smi.y:220 220 if (objectPtr->nodePtr->parentPtr && (gdb) where #0 0x40037b15 in checkObjects (parserPtr=0xbffff5f0, modulePtr=0x80559a0) at parser-smi.y:220 #1 0x4003a26c in smiparse (parserPtr=0xbffff5f0) at parser-smi.y:1641 #2 0x40031021 in loadModule ( modulename=0xbffff841 "mibs/ietf/DOT12-RPTR-MIB", parserPtr=0x0) at data.c:3792 #3 0x40035110 in smiLoadModule (module=0xbffff841 "mibs/ietf/DOT12-RPTR-MIB") at smi.c:416 #4 0x080492f2 in main (argc=2, argv=0xbffff6f4) at smilint.c:314 #5 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 (gdb) print objectPtr->nodePtr->parentPtr $1 = (struct Node *) 0x62696d2f Running with ElectricFence and EF_PROTECT_BELOW on turns up a problem, if that helps. I can provide details if that would help.

2 2

smidump perl output module naive about backslashes
by Allen McIntosh 26 Apr '05

26 Apr '05

The "perl" output module in smidump seems to be a little naive about backslashes. (Given the output language, I can understand a little difficulty in getting all the special characters escaped correctly.) Rather than trust the offending string to a mailer, I've included it as an attachment. It's taken from CISCO-SLB-EXT-MIB.my, which is part of the CISCO MIB collection. The perl output won't compile, and the problem seems to be that '\' gets rendered as \'\\' (the backslash in the middle isn't being doubled). This problem was found with version 0.4.3, running on Linux/x86. [I may wind up fixing this one myself while fixing another problem. Look for a post about the joys :-) of HP-UX in a few days.] SlbRegularExpression ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "A regular expression of length 0 to 255. Regular expressions are typically used for matching fields in Layer 7 data streams, such as URLs or Cookies in HTTP. The following syntax is based on the file name matching algorithm commonly employed in UNIX : '*' matches zero or more characters; '?' matches exactly one character; '\' means escaped character, e.g., '\*' matches the character '*'; a bracketed range matches any single character from the range, e.g. [0-9] matches '0', '2', and '9', but not 'a'; a leading ^ in a range means don't match any in the range; '+' matches any sequence of one or more characters; '.' matches any single character; All other characters represent themselves. '\a' matches alert (ASCII 7); '\b' matches backspace (ASCII 8); '\f' matches form-feed (ASCII 12); '\n' matches newline (ASCII 10); '\r' matches carriage return (ASCII 13); '\t' matches tab (ASCII 9); '\v' matches vertical tab (ASCII 11); '\0' matches null (ASCII 0); '\\' matches backslash; '\x##' matches the ASCII character whose hexadecimal representation is ##. " SYNTAX OCTET STRING (SIZE (0..255))

2 4

Doubts regarding smidump data structures
by Pamidipati Suresh-G20238 22 Apr '05

22 Apr '05

Hi, Smidump uses the data structures Module, Object, Type, List for storing the information as defined in the ASN.1 MIB/SMI files. I have a doubt how the List pointer of the Type structure is assigned a value. I have seen that for Syntax like xyzTableEntry (which is a SEQUENCE containing all the columns of xyzTable), Type structure is created and List pointer contained in this structure points to linked list of nodes, each node corresponding to a column of the table. I mean to say if there are 'n' elements present in the SEQUENCE xyzTableEntry, ListPtr points to 'n' number of nodes. Also if there is any object having the syntax like INTEGER {1,2,3,4} (enumeration), then for this syntax also, Type structure contains List ptr pointing to list of 4 nodes. Now I have the questions. 1.The Type structure for Syntax like Guage, Integer, IpAddress, and others also contains List pointer pointing to one node. 2. And there is a Textual convention RouterId defined in OSPF-MIB whose syntax is defined as IpAddress. But the Type structure built for this RouterId contains List ptr pointing to NULL (0x0). Why is this so..? Any information explaining this will be greatly appreciated. Regards, suresh.

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 April 2005