[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mibble-users] Mibble 2.2 fails to flag bad syntax of a MIB variable
From: |
rks |
Subject: |
[Mibble-users] Mibble 2.2 fails to flag bad syntax of a MIB variable |
Date: |
Thu, 13 Nov 2003 13:00:40 -0800 (PST) |
Thank you, that works (I should have seen the cause of the defect).
Anyways, I have a different question now: how pedantic
is this MIB parser? In comparison with SMIC and net-snmp parser?
I find that it fails to detect the following error in the MIB:
// File: CISCO-AAA-SERVER-MIB.my
//...
CasConfigEntry ::=
SEQUENCE {
--casProtocol CiscoAAAProtocol,
casProtocol INTEGER,
//...
}
casProtocol OBJECT-TYPE
SYNTAX CiscoAAAProtocol
MAX-ACCESS not-accessible
//...
::= { casConfigEntry 1 }
//...
$ java net.percederberg.mibble.MibbleValidator ./CISCO-AAA-SERVER-MIB.my
Reading ./CISCO-AAA-SERVER-MIB.my... [OK]
Files processed: 1
with errors: 0
with warnings: 0
$
Am I missing something or is this another bug? CiscoAAAProtocol is a
locally defined textual convention with the base syntax of INTEGER.
Thanks,
Rk
x77309
On Thu, 13 Nov 2003, Per Cederberg wrote:
> On Thu, 2003-11-13 at 00:34, address@hidden wrote:
> > I already checked the code of MibbleValidator
> > before writing the list and thought that the
> > code was adding the directory of the specified
> > MIB file to the MibLoader path:
> >
> > > loader.addDir(file.getParentFile());
> >
> > DOes not this line add the dir of the specified
> > MIB file to the MibLoad path?
>
> Oh, sorry... I was in a bit of a hurry yesterday,
> so I didn't really answer your question, did I?
>
> Looking closer at your case, it looks like you
> have found a bug. It seems that the getParentFile()
> method doesn't return anything useful if the
> file name didn't have a directory portion.
>
> As a workaround, run MibbleValidator like this
> instead:
>
> java net.percederberg.mibble.MibbleValidator ./CISCO-TC.txt
> ^^
>
> Seems I've only ever tried validating files by
> specifying some directory name (like when using
> find or similar).
>
> Sorry for the inconvenience this caused you. And
> again, sorry for not reading your question properly
> the first time around. I've registered bug #6528
> for this issue:
>
> http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=6528&group_id=4522
>
> Cheers,
>
> /Per
>
>
>