elwood writes:
> More than half a dozen times today my students managed to
> irretrievably hang the IDL workbench.
> They were running a while loop within their program.
> No syntax error was issued, but when they ran the program it would not
> execute.
> And the idl command-line prompt went grey.
>
> ctrl-c did not get them out of this state
> reset perspective did not get them out of this locked-up state
>
> I wish I could give you more hints, but its unclear what is causing
> this problem.
> It is not an infinite loop.
How do you know? That's what it sounds like to me. See below.
> Out of desperation they killed the workbench entirely by clicking on
> the little close x for the window.
> And then went to Windows XP task manager and killed the idl task.
>
> Has anyone else noted this problem?
> Is there another method of getting IDL out of a locked-up state?
I'm no huge fan of the Workbench, but this sounds strange.
Honestly, it sounds more like bad CATCH error handling to me. Does
everyone have a CATCH, /CANCEL as the first line of their
CATCH error handler?
I've taught several cl***** on the Workbench, and I haven't
run into problems like this, although one guy was rebooting
all the time. He never let me see the reason for that, so
I assume it was something he was doing, not IDL.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming (www.dfanning.com)
Se****e ma de ni thui. ("Perhaps thou speakest truth.")
|
