public inbox for
 help / color / mirror / Atom feed
From: Mike Clarkson <>
To: Syd Polk <>, Mike Fahlbusch <>
Cc:, Left Spin <>
Subject: Re: Debugging SourceNavigator
Date: Fri, 14 Dec 2001 11:14:00 -0000	[thread overview]
Message-ID: <> (raw)
Message-ID: <20011214111400.-Plf5ZFKvf2zoKledH3Slc39jZ6zZYF8DIypp4dfIsQ@z> (raw)
In-Reply-To: <>

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.


  reply	other threads:[~2001-12-14 11:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24 14:01 Left Spin
2001-11-24 14:40 ` Mike Fahlbusch
2001-11-26  0:23   ` Syd Polk
2001-11-29 23:46     ` Mike Clarkson [this message]
2001-12-14 11:14       ` Mike Clarkson
2001-12-12 22:52     ` Syd Polk
2001-12-12 18:03   ` Mike Fahlbusch
2001-12-12 17:19 ` Left Spin
  -- strict thread matches above, loose matches on Subject: below --
2001-11-25 18:28 Left Spin
2001-12-12 18:06 ` Left Spin
2001-11-23 14:19 Left Spin
2001-11-27 17:10 ` Mike Clarkson
2001-12-14  9:25   ` Mike Clarkson
2001-12-12 17:18 ` Left Spin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).