[tkined] Memory corruption with TCL 8.0.4 and Scotty 2.1.10 on Solaris??

Judah Greenblatt (judah@bbt.com)
Fri, 09 Apr 1999 11:36:21 -0400

I recently upgraded from TCL 7.6 to TCL 8.0.4 for a large
Scotty agent, and I think I'm seeing memory corruption
within TCL.

The platform:
Hardware: Sparc 5
OS: Sun Solaris 2.5.1
TCL: 8.0.4 straight from Scriptix
Scotty: 2.1.10 modified to bind specific local ethernet addresses
Shared libraries used for Tcl, TK, Tnm

Symptom:

I have a binding like:
$session bind fooEntry commit {fooFunc fooEntry %i}
$session instance fooItem.1.2 myArray(fooItem.1.2) XX

when the agent receives a set request for
MIB entry fooItem.1.2 (where fooItem is a child of fooEntry
in the mib), fooFunc is called:
fooFunc fooEntry xxfooBar fooBletch
where "fooBar" and "fooBletch" are other columns in table fooEntry.

It looks like the varBind for fooItem.1.2 has become corrupted
inside scotty at the point that the Scotty internal
call to the mib binding substitutes %i.

This happens repeatable at a certain point in a large test script,
but no place else. The only thing I am doing in that test script
that is odd is there are a large number of "after idle" events
queued up (perhaps 20 or 30).

Has anyone seen anything like this before?

The code works just fine on Tcl 7.6.

-- 
Judah Greenblatt	judah@bbt.com     919-405-4716
BroadBand Technologies, Durham, NC
--
!! 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.