comp.lang.idl-pvwave archive: archive » Re: IDL on Windows vs. Unix, debugging consideration

Home » Public Forums » archive » Re: IDL on Windows vs. Unix, debugging consideration

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: IDL on Windows vs. Unix, debugging consideration [message #40372]

Sun, 08 August 2004 15:26

Mark Hadfield
Messages: 783
Registered: May 1995

Senior Member

Ben Panter wrote:
> R.G. Stockwell wrote:
>
>> You do know that in windows it is Control-Break, not control-C right?
>> I assume you meant that. I find that it often stops when you ask it to,
>> under windows. However a tight loop will ignore you. Perhaps a
>> wait command deep in the loop, with the smalles wait possible would help
>> [in a debuggin situation].
>
>
> I've used the following to stop runaway code in the IDLDE...
>
> # press the "break" button (which gets ignored)
> # attempt to close the IDLDE environment
> # reply "no"
>
> It then appears to process the break command *before* it restarts the
> program. This method has worked for me a number of times, although no
> guarantee is offered!

Clever!

If you know beforehand that your code might run away and you want to put
in an interruptible point (as distinct from a break point) the following
will do nicely:

void = widget_event(/NOWAIT)

--
Mark Hadfield "Ka puwaha te tai nei, Hoea tatou"
m.hadfield@niwa.co.nz
National Institute for Water and Atmospheric Research (NIWA)

# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #
# More included text than new text. Blah blah. #

Report message to a moderator

[Message index]

		Re: IDL on Windows vs. Unix, debugging consideration By: Mark Hadfield on Sun, 08 August 2004 15:26
		Re: IDL on Windows vs. Unix, debugging consideration By: Ben Panter on Sat, 07 August 2004 01:38
		Re: IDL on Windows vs. Unix, debugging consideration By: R.G. Stockwell on Fri, 06 August 2004 18:24
		Re: IDL on Windows vs. Unix, debugging consideration By: Michael Wallace on Thu, 05 August 2004 20:47
		Re: IDL on Windows vs. Unix, debugging consideration By: David Fanning on Thu, 05 August 2004 13:00
		Re: IDL on Windows vs. Unix, debugging consideration By: Michael Wallace on Thu, 05 August 2004 12:48
		Re: IDL on Windows vs. Unix, debugging consideration By: David Fanning on Thu, 05 August 2004 10:31

Previous Topic:	Histogram question
Next Topic:	Saddam Hussein Found hanging in Jail Cell

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Nov 30 06:10:42 PST 2025

Total time taken to generate the page: 0.19614 seconds