Hi,
When running smidump on http://mibbinator.org/mibindex/extracted/BGP4V2-MIB-idr-08.txt and outputting in python format, the node after bgp4V2Groups has ASCII text instead of a Node data structure, causing smiGetNextNode() to crash.
1613 nodePtr = nodePtr->nextPtr; $30 = (Node *) 0x57c600 (gdb) x/s $30 0x57c600: "}, # node\n"
This is the last line that was output, I think because this Node was freed and so smiVasprintf is using the same memory area for line buffering, but there were still pointers to it.
I will admit to running with "-k", to ignore the "mib-2 XXX" error in this MIB; this works with -f identifiers but seems to be the killer for -f python/perl/yang.
When the { mib-2 XXX } is replaced by { mib-2 9999 }, the python/ perl/yang outputs succeed.
In my use case (getting python access to the structure of a MIB in an Internet Draft), I need the output to work in this case. This worked some time ago (unfortunately I didn't practice good revision control and don't know exactly which version broke this; I developed the functionality that required this behavior in mid-2007).
Any ideas where to look to find out what is freeing this node? (I tried --enable-dmalloc but the dmalloc linkage didn't work)
Thanks, Bill