On Feb 26, 2004, at 12:33 AM, Landon Fuller wrote:
This suggestion obviously requires a bit of knowledge about Tcl
internals,
but it works well enough for just me: Run Tcl under gdb; break on the
Tcl
functions you want to examine more closely.
While that's in the category of "just barely getting you there", it's
really not a substitute for a decent Tcl debugger. For one, it doesn't
allow you to easily watch variables or set trace traps for when they
change, nor can you set arbitrary breakpoints and look at the stack
traces leading up to those functions for each time you hit the
breakpoint. What you propose is essentially the equivalent of using a
hardware front panel to debug assembly code. Yeah, I've done that too,
but it's not much fun. :-)
The idea of not catch'ing the portexec when -d is specified is also a
fine one.
--
Jordan K. Hubbard
Engineering Manager, BSD technology group
Apple Computer
|
