Hi Robert,
 
Can you please provide a full example?  If I try the tcl_sample.tcl file that
ships with Komodo (available in the sample project), I cannot confirm any
problem with locals.  If I set a breakpoints at line 21 (::set ::var "I'm a
string") and select Go (F5), then when the breakpoint is hit, I see $feather
as a local (as expected).  If you find some discrepancy, please report it at
http://bugs.activestate.com/.

Regards,

  Jeff Hobbs
  http://www.ActiveState.com/, a division of Sophos 

-----Original Message-----
From: komodo-discuss-bounces@[...].com
[mailto:komodo-discuss-bounces@[...].com] On Behalf Of Bartis,
Robert M (Bob)
Sent: April 30, 2005 1:04 PM
To: 'Komodo-discuss@listserv.ActiveState.com'
Subject: [Komodo-discuss] Local variables intermittently work up in debugger


Has anyone see an issue with the current version of the Komodo debugger where
local variable do not show up in the debugger. When setting a break point on
the STRDBSQL:: statement below I would have expected to be able to view
currEOIs , mappedEOIs, etc. Is this a known issue? Is this the correct list to
ask the question to?


proc eoiMapping::commitEOIs {} {
    set currEOIs [STRDBSQL::eoiByRelease [selectedRelease] -flatlist]
    set mappedEOIs [eoiMapping::mappedEOIs]
    
    set testPlanKey [STRDBSQL::testPlanKey [selectedRelease] -flatlist]
 
    foreach eoi $mappedEOIs {
# Search the current EOI list from the database. If the eoi
 # from the users mapped list is not present than add it to the
 # DB now.
 if {[lsearch $currEOIs $eoi] == -1} {lappend newRows "$testPlanKey $eoi"}
    }
    
    if {[info exists newRows]} {
 STRDBSQL::insert plantriggers {testplan_intro_PlanID_FK eoi_Number_FK}
$newRows
    }
   return 0 
}