[Tclpro-dev] (Fwd) Re: Problem with using TclPro1.5 with an Embedded applic

[William J. N. <bn...@mi...>]

------- Forwarded message follows -------
To:             	"William J. Noonan" <bn...@mi...>
Copies to:      	he...@pa... (Melissa Chawla), tcl...@li...
Subject:        	Re: Problem with using TclPro1.5 with an Embedded application
From:           	Brent Welch <we...@pa...>
Date sent:      	Wed, 12 Dec 2001 22:00:53 -0800

Ah ha!  I finally decided to test your problem, and indeed there is
some non-8.0 friendly Tcl code in our Debug Nub.  If you use the
Super-Burrito menu and enable debug logging, you'll see the error 
message.

'SEND 1 {DbgNub_GetVariables 1 {}}'
LOG(message,941019064): reading 35 bytes
LOG(message,941020087): got: 'RESULT {{x s} {y s} {args s} {w s}}'
LOG(message,941021467): sent: len=41 'SEND 1 {DbgNub_GetVar 1 213 {x 
y args w}}'LOG(message,941022466): reading 293 bytes
LOG(message,941023441): got: 'ERROR {expected integer but got "end"} 
1 NONE {expected integer but got "end"
    while executing
"string index $var end"
    (procedure "DbgNub_GetVar" line 28)
    invoked from within
"DbgNub_GetVar 1 213 {x y args w}"
    ("eval" body line 1)
    invoked from within
"eval [lindex $msg 2]"}'

I'm not sure if the debug nub is easily fixable in the 1.5 
distribution -
it may be that things are all wrapped up.  I am super busy at the 
moment,
but you might find someone on the tcl...@li... mailing list
to help.

>>>"William J. Noonan" said:
 > Dear Brent,
 > 
 > I am revisiting the problem I had with the TclPro debugger when I 
try to
 > connect it remotely.  I can connect up with the EDA (Electronic 
Design
 > Automation) application, but cannot view any variables in my code. 
 > 
 > The EDA application is expecting to run with tcl 8.0. The 
"init.tcl" file
 > installed with the EDA tool requires -exact tcl 8.0. 
 > 
 > I did notice the TclPro debugger would only function properly when 
the
 > interpreter  was set to "protclsh83" when debugging code examples 
 > (code outside the EDA tool environment). When I had set it to our 
 > "/usr/local/bin/tclsh" version 8.0, the debugger exhibited the 
same behavior
      ( 
 > control over the execution of code but, could not view values of 
variables).
 > 
 > Does the debugger rely on using protclsh83 ? 
 > 
 > Do I need to make some changes to the EDA application's 
installation ?
 >   (for example putting or installing the tcl8.3 init.tcl file 
(from tclpro's
      package) 
 > into the EDA tool's package.)
 > 
 > Any help would greatly be appreciated.
 > 
 > 
 > Thanks you for your time.
 > 
 > 
 > Bill Noonan 
 > 
 > ----------------------------------
 >  Bill Noonan
 >  Advanced ASIC Development
 >  550 Willowbrook Office Park
 >  Fairport, NY 14450
 >  Mint Technology
 >  Phone: 716-249-8539
 >  email: bn...@mi...
 > ----------------------------------

--
Brent Welch
Software Architect, Panasas Inc
Pioneering Smart and Infinitely Scalable Storage Networks

www.panasas.com
we...@pa...


------- End of forwarded message -------
----------------------------------
 Bill Noonan
 Advanced ASIC Development
 550 Willowbrook Office Park
 Fairport, NY 14450
 Mint Technology
 Phone: 716-249-8539
 email: bn...@mi...
----------------------------------