RE: [tkined] Core dump getting index of a TC-defined object

From: Don Goodspeed (dgoodspe@timetra.com)
Date: Thu Jun 07 2001 - 21:14:51 MET DST

I was able to remove my *.idy files and this fixed the problem. I'll
include more info next time. I just wanted to see if anyone else had seen a
similiar problem in the past.

-don

>>>>> Don Goodspeed writes:

Don> First off, I'm running the latest CVS code as of June 5th, 2001,
Don> but I first saw this problem with 2.1.10. My operating system is
Don> Red Hat Linux 6.2. My TCL version is 8.3.2.

Don> I've got a proprietary MIB attribute in one table (let's call it
Don> xTableAttribute) that is defined with a Textual Convention (let's
Don> call it XTCName) imported from another MIB module.

Don> In that second MIB module there is a table called xTCNameTable
Don> which is index'ed by xTCName which is also defined as the textual
Don> convention XTCName.

Don> The textual convention itself, XTCName, is defined as an
Don> Unsigned32.

Don> When I execute [Tnm::mib index xTableAttribute], I get a core
Don> dump.

Don> When I execute [Tnm::mib syntax xTableAttribute], I get SEQUENCE.

Don> Any thoughts? 

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.

This archive was generated by hypermail 2b29 : Thu Jan 03 2002 - 14:56:27 MET