[news.eclipse.technology.dltk] Re: Tcl/Tk Debug_tool not working well in

[Alex Panchenko <alex@xxxxxxxxx>]

Hi Jin,

Thanks for reporting this bug. I was able to reproduce it.

It occurs when there is some internal command active (e.g. a few 
internal commands are sent to refresh Variables view) and user executes 
 e.g. Step Into/Step Over.

It looks like this debugger does not support multiple commands at the 
same time - quite strange that we did not notice that issue before.

The bug is registered at 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=239679
It will be fixed in the nearest future.

Until this bug is fixed you can

a) turn off global variables display (via drop down menu in the top 
right of the Variables view) so the commands needed to refresh variables 
view will be executed faster.

b) do not press F5/F6 too fast

Thanks,
Alex


Jin wrote:
> Hello,
>
> I've finally installed the DLTK plug-in for developing tcl in eclipse.
> The problem for debugging tcl is that eclipse only support the debug 
> tool from
> komodo---dbgp_tcldebug and when i debug a tcl file, the tool doesn't 
> work well:
> it always exit at several "step forward" operations.
> Here is the output message:
>
> Execution error: 998
> ::engine::Snit_inst1::dbg step called with an app that is not stopped.
>    while executing
> "# Compiled -- no source code available
> error "called a copy of a compiled script""
>    (procedure "::dbgtalk::Snit_methodstep" line 1)
>    invoked from within
> "# Compiled -- no source code available
> error "called a copy of a compiled script""
>    (procedure "::dbgp::step::Snit_methodDoStepOver" line 1)
>    invoked from within
> "::dbgp::client::Snit_inst1::stepper DoStepOver step_over {-i 397}"
>    ("uplevel" body line 1)
>    invoked from within
> "uplevel 1 [linsert $args 0 $self]"
>    invoked from within
> "::snit::RT.CallInstance ::dbgp::step::Snit_inst1 DoStepOver step_over 
> {-i 397}"
>    ("eval" body line 1)
>    invoked from within
> "# Compiled -- no source code available
> error "called a copy of a compiled script""
>
> BTW, the exit could appear at any random place of the source code. I 
> didn't find any clue where it always happen.
> Anyone know what's going on here? How could i fix or avoid this? 
> Appreciate!
>
> Jin