I have tested the r34468 patch together with 0.4.8 and it works. Thanks!
//Göran
-----Original Message----- From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] Sent: den 23 mars 2011 14:50 To: Göran Runfeldt Cc: libsmi@ibr.cs.tu-bs.de Subject: Re: [libsmi] Problem with overlapping ranges with the same minimum value
On Wed, Mar 23, 2011 at 09:21:56AM +0100, Göran Runfeldt wrote:
I have found a problem when using smidump 0.4.8 with certain MIB files. The MIB file from this example is private, so I have extracted the part that causes the problem:
[...]
The problem was identified to be caused by the same minimum value (16) in the two ranges. Smidump correctly warns about overlapping ranges, but this code was added to keep smidump from looping when using the -k option:
I decided to handle this somewhat different (r34468). The library now translates (smidump -k -f xml)
TestLabel ::= Unsigned32(16..8191|16..1048575|16..8191)
into this:
<typedef name="TestLabel" basetype="Unsigned32"> <range min="16" max="8191"/> <range min="16" max="1048575"/> <range min="16" max="8191"/> </typedef>
/js