Re: Debugging SourceNavigator

[Mike Clarkson <support@internetdiscovery.com>]

At 10:50 PM 12/12/01 -0800, Syd Polk wrote:
>
>
>Mike Fahlbusch wrote:
> 
>> >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr
>> >tcl/tk], but now I'm at a loss on how you debug the running application.
>
>There is no good way to step SN through a debugger. I would investigate
>setting the SN_DEBUG variable and using the logging. I have also spent
>time actually in gdb with the C code for the Tcl interpreter figuring
>out problems.

With Tixinspect you are debugging the run-time program by connecting to it
with Tk's send mechanism. After making the SN interpreter "visible" to send
by doing the steps I outlined previously, use File/Select Interpreter/
and look for the interpreter named SN#xxxx where xxxx is the window id.

>> >I'm having trouble following the state variables of the megawidgets, and
>> >I'd really like to be able to set break points in the tcl/tk code and
>> >examine objects.
>
>One thing you can do is launch the console, load the SN part, and then
>selectively replace the pieces you need. tk is a dynamic coding
>environment, and you should be able to take advantage of that.

With Tixinspect use Tcl/TixDebug to bring up the debugger, then click on
Refresh. It takes advantage of the fact that tk is a dynamic coding
environment, and selectively replace the pieces you choose with instrumented
procedures that activate the debugger. You can set breakpoints, or step
through procedures.

Mike.