Blog

An error could occur when propagating name changes in a container record (such as a module) to other contained records whose property workspaces are also open. In the SDK, a stack overflow error/crash could occur when assigning an OID value to a conformance module. These problems are corrected in the 2.3.6 release of MIB Smithy.

Several errors that could occur while using various features of the MIB Smithy’s Files Tree in the Project Panel, particularly on Windows, were fixed in this patch release.

Changes made in MIB Smithy SDK 2.3.3 to migrate to Tcl_Obj APIs broke the results returned by the SMI database “find” command and have been fixed in this patch release.

A new -members query option was added for compliance, capability and conformance module records to return the unified results of both the -cgroups and -variations query options for those record types.

Significant Changes (MIB Smithy)

• The labels for items in the Project Tree with OID values now include the subidentifier for the item. Top-level items in a module’s tree display the as much of the OID has can be determined based on loaded modules and known dependencies.
• Numerous improvements to conversion between SMI versions: User is now asked for confirmation before converting a top-level node to a MODULE-IDENTITY. Modules are automatically validated after conversion. Changes to IMPORTS are handled better. Table SEQUENCE typedefs are better converted. Plus several bug fixes such as Integer32 -> INTEGER when converting from SMIv2 to SMIv1.
• Ok/Apply/etc. buttons at the bottom of workspace are now last in the tab focus order.
• Append button in display-hint wizard is now last in its focus order.

Miscellaneous Bug Fixes (MIB Smithy)

• An error could occur when using the MIB Browser SNMP tool and expanding a branch containing column instances with multiple subidentifiers such as might occur with an OCTET STRING index.
• The subtype/refinement properties (range/enums/etc.) would fail to take focus via the tab key due to a race condition.
• Corrected “invalid command name” error that could occur applying changes to MODULE-COMPLIANCE variations.
• Setting an OID value for a record that would create a recursive reference could generate a “path does not exist” error upon refreshing the project tree.
• An error could occur when launching the Table Wizard without an appropriate parent (in OID space) record selected.
• Corrected checking for whether or not a redraw is required upon notebook page addition when the page tab is won’t fit in available space.
• Modified combobox controls to create their popup lists on-demand rather than on-creation in order to avoid running into a race condition that exists in Tcl/Tk (Bug # 767176 at SourceForge).
• Corrected “not a notification” dialog that could pop up trying to add notifications to a notification group due to a copy & paste error.
• Corrected minor display issue in the project tree with implicit node definitions beneath non-node records (e.g. MODULE-IDENTITY statements), which showed the wrong icon.

Significant Changes (MIB Smithy SDK)

• Added check for AUGMENTS referencing another table that uses AUGMENTS rather than the base table.
• Changed dependency error for types referenced by variations to warnings for consistency with other dependency warnings.
• Added validation warning for unused imported symbols.
• Removed all use of Tcl_DString, migrating instead to proper Tcl_Obj’s for results etc. for efficiency. Changes also fixed a bug in the result format for string default values returned by “smilib get -defval”.
• Added a -members option for compliance, capability and conformance module records to return the unified results of both -cgroups and -variations.

Miscellaneous Bug Fixes (MIB Smithy SDK)

• Fixed bug in tracking of unique IDs for SNMP requests sent using non-blocking mode.
• Certain operations or setting certain record property synonyms could leave the internal OID tree/index stale (i.e., not up to date). The methods to determine when and what needs to be reindexed should be much more robust.
• CRCRLF end-of-line sequences (yes, that’s two CR’s) in comments no longer generate an “unrecognized token or symbol” error from the parser. Extra CR’s are treated as whitespace and silently dropped.
• Removed invalid options from compliance properties (smilib get) that aren’t applicable to the record type and generated a “not implemented” error rather than listing available options as normal.