Has insight (0823 snapshot) been freezing up for anyone else.

Has insight (0823 snapshot) been freezing up for anyone else.

[Moses DeJong]

Hi all.

I have tried to debug a couple of programs with the new 19990823 snapshot
of insight but it keeps freezing up. I am running RedHat Linux 5.2 on
an intel system. I was not getting these freezups with the 2nd to last
snapshot so I think something must have changed recently. When insight
freezes the Tk event loop is still running (Tk will still redraw exposed
windows), but I can not click on insight buttons or anything (the
"stopwatch" is shown for the pointer and button clicks do not seem to do
anything). When I try to attach a debugger to the insight executable I
just end up in a __select method and there does not seem to be a stack
indicating how the program got there. Is anyone running into this?

thanks
Mo DeJong
dejong@cs.umn.edu

Re: Has insight (0823 snapshot) been freezing up for anyone else.

[James Ingham]

Moses DeJong writes:

 > 
 > I have tried to debug a couple of programs with the new 19990823 snapshot
 > of insight but it keeps freezing up. I am running RedHat Linux 5.2 on
 > an intel system. I was not getting these freezups with the 2nd to last
 > snapshot so I think something must have changed recently. When insight
 > freezes the Tk event loop is still running (Tk will still redraw exposed
 > windows), but I can not click on insight buttons or anything (the
 > "stopwatch" is shown for the pointer and button clicks do not seem to do
 > anything). When I try to attach a debugger to the insight executable I
 > just end up in a __select method and there does not seem to be a stack
 > indicating how the program got there. Is anyone running into this?
 > 
 > thanks
 > Mo DeJong
 > dejong@cs.umn.edu
 > 
 > 

What have you been doing?  I tried a bunch of simple things on a
RedHat 5.2 box, and it seemed to work fine.

Jim

-- 
++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
Jim Ingham                                              jingham@cygnus.com
Cygnus Solutions Inc.

Re: Has insight (0823 snapshot) been freezing up for anyone else.

[Moses DeJong]

On Wed, 1 Sep 1999, James Ingham wrote:

> Moses DeJong writes:
> 
>  > 
>  > I have tried to debug a couple of programs with the new 19990823 snapshot
>  > of insight but it keeps freezing up. I am running RedHat Linux 5.2 on
>  > an intel system. I was not getting these freezups with the 2nd to last
>  > snapshot so I think something must have changed recently. When insight
>  > freezes the Tk event loop is still running (Tk will still redraw exposed
>  > windows), but I can not click on insight buttons or anything (the
>  > "stopwatch" is shown for the pointer and button clicks do not seem to do
>  > anything). When I try to attach a debugger to the insight executable I
>  > just end up in a __select method and there does not seem to be a stack
>  > indicating how the program got there. Is anyone running into this?
>  > 
>  > thanks
>  > Mo DeJong
>  > dejong@cs.umn.edu
>  > 
>  > 
> 
> What have you been doing?  I tried a bunch of simple things on a
> RedHat 5.2 box, and it seemed to work fine.
> 
> Jim
> 
> -- 
> ++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
> Jim Ingham                                              jingham@cygnus.com
> Cygnus Solutions Inc.
> 



I have not been able to reproduce the "frozen stopwatch" problem
with a set series of steps, but I was able to consistently
generate an error that seems to do the same thing. I was
running insight on the 1.01 version of jikes while doing
the following.

I set a breakpoint at contol.cpp line 549.
I ran the program, and hit the continue button to start it up.
Once I hit the breakpoint, I pressed the step button a couple
of times until I was inside the inlined operator[] C++ method.
At this point I was in the inlined method defined in tuple.h
line 188. I then highlighted a pointer and chose the
"dump memory" option from the drop down list over the selection.
I then clicked the up button on the spin widget next to the
address which generated this Tcl error.

A parse error in expression, near '-1 * 16'

	while executing
"gdb_cmd "printf \"%u\", $current_addr + $num * $bytes_pre_row""
	(object "::.memwin0.memwin" method "::MemWin::incr_addr" body line 9)
	invoked from within
"::.memwin0.memwin incr_addr -1"
	("after" script)
errorCode is NONE


When this error is generated, the default Tk error dialog box shows
up to display the error message. Problem is, the error window now
ignored button clicks and key press events. The other insight windows
also ignore key press and mouse events, but the Tk event loop is
still running because the windows still redraw when that get expose
events. I also noticed that if you close the main insight window the
"do you want to stop the debugger (Yes) (No)" dialog shows up.
I was able to get a stack trace from insight while it was stuck,
and it seemed to indicate the Tk_TkwaitCmd was getting called
before the application got stuck.


Here is the stack trace.

#0  0x4017c2de in __select ()
#1  0x8299434 in notifier ()
#2  0x81e2010 in Tcl_DoOneEvent (flags=0)
    at ../../../tcl/unix/../generic/tclNotify.c:726
#3  0x81a8f4f in Tk_TkwaitCmd (clientData=0x82c0150, interp=0x82ac8f8, 
    argc=3, argv=0xbfffe17c) at ../../../tk/unix/../generic/tkCmds.c:692
#4  0x81b4cc7 in TclInvokeStringCommand (clientData=0x82c3508, 
    interp=0x82ac8f8, objc=3, objv=0x82ad598)
    at ../../../tcl/unix/../generic/tclBasic.c:1745
#5  0x81cc854 in TclExecuteByteCode (interp=0x82ac8f8, codePtr=0x939cfa0)
    at ../../../tcl/unix/../generic/tclExecute.c:955
#6  0x81b5493 in Tcl_EvalObj (interp=0x82ac8f8, objPtr=0x91da008)
    at ../../../tcl/unix/../generic/tclBasic.c:2645
#7  0x81e73e2 in TclObjInterpProc (clientData=0x8d87458, interp=0x82ac8f8, 
    objc=8, objv=0x82ad578) at ../../../tcl/unix/../generic/tclProc.c:996
#8  0x81cc854 in TclExecuteByteCode (interp=0x82ac8f8, codePtr=0x9339ad8)
    at ../../../tcl/unix/../generic/tclExecute.c:955
#9  0x81b5493 in Tcl_EvalObj (interp=0x82ac8f8, objPtr=0x91d9fa8)
    at ../../../tcl/unix/../generic/tclBasic.c:2645
#10 0x81b8656 in Tcl_EvalObjCmd (dummy=0x0, interp=0x82ac8f8, objc=2, 
    objv=0x82ad570) at ../../../tcl/unix/../generic/tclCmdAH.c:484
#11 0x81cc854 in TclExecuteByteCode (interp=0x82ac8f8, codePtr=0x93d0dd0)
    at ../../../tcl/unix/../generic/tclExecute.c:955
#12 0x81b5493 in Tcl_EvalObj (interp=0x82ac8f8, objPtr=0x939b700)
    at ../../../tcl/unix/../generic/tclBasic.c:2645
#13 0x81e73e2 in TclObjInterpProc (clientData=0x93cd270, interp=0x82ac8f8, 
    objc=2, objv=0x82ad568) at ../../../tcl/unix/../generic/tclProc.c:996
#14 0x81cc854 in TclExecuteByteCode (interp=0x82ac8f8, codePtr=0x93abe38)
    at ../../../tcl/unix/../generic/tclExecute.c:955
#15 0x81b5493 in Tcl_EvalObj (interp=0x82ac8f8, objPtr=0x91d9d98)
    at ../../../tcl/unix/../generic/tclBasic.c:2645
#16 0x81b52a0 in Tcl_Eval (interp=0x82ac8f8, string=0x93a30e0 "bgerror {}")
    at ../../../tcl/unix/../generic/tclBasic.c:2453
#17 0x81b677f in Tcl_GlobalEval (interp=0x82ac8f8, 
    command=0x93a30e0 "bgerror {}")
    at ../../../tcl/unix/../generic/tclBasic.c:3983
#18 0x81cb6f3 in HandleBgErrors (clientData=0x933c6e0)
    at ../../../tcl/unix/../generic/tclEvent.c:243
#19 0x81e8128 in TclServiceIdle ()
    at ../../../tcl/unix/../generic/tclTimer.c:681
#20 0x81e205d in Tcl_DoOneEvent (flags=0)
    at ../../../tcl/unix/../generic/tclNotify.c:760
#21 0x815fa74 in Tk_MainLoop ()
    at ../../../tk/unix/../generic/tkEvent.c:1041
#22 0x809795a in tk_command_loop () at ../../gdb/gdbtk-hooks.c:382
#23 0x80dfc9c in main (argc=1, argv=0xbffff964) at ../../gdb/main.c:681



I hope that helps
Mo DeJong
dejong@cs.umn.edu