comp.lang.idl-pvwave archive: archive » Re: .trace not working?

Home » Public Forums » archive » Re: .trace not working?

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

Re: .trace not working? [message #67605 is a reply to message #67604]

Wed, 05 August 2009 14:16

BLemire@ittvis.com
Messages: 9
Registered: March 2009

Junior Member

On Aug 5, 2:13 pm, Bruce Bowler <bbow...@bigelow.org> wrote:
> Environment IDL 7.0 (and 7.1) on fedora 10 (and fedora 11), 32 bit version
>
> Imagine, if you will, a simple .pro file such as the following (never
> mind that this doesn't really do anything)...
>
> pro test1
> x = randomn(seed1, 16)
> y = randomn(seed2, 16)
> plot, x, y
> end
>
> Now imagine that you fire up IDL and type the following commands at the
> IDL> prompt
>
> breakpoint,"test1.pro",2
> test1
>
> and further, attempt to stretch you imagination to the point that, when
> you get to the IDL prompt as a result of the breakpoint, you type
>
> .trace
>
> You, of course, type that particular command because the documentation
> says, and I quote,
>
> .TRACE - Similar to .CONTINUE, but displays each line of code
> before execution.
>
> but when you hit the return key at the end of .trace, you see no
> additional outputting of code prior to executing each line of code.
>
> Where have you gone wrong???
>
> Bruce
>
> --
> +-------------------+--------------------------------------- ------------+
> Bruce Bowler | I am free of all prejudices; I hate everyone
> 1.207.633.9600 | equally. - W. C. Fields
> bbow...@bigelow.org |
> +-------------------+--------------------------------------- ------------+

Bruce,

Based on the documentation in IDL 70 and IDL 71 the following
description is provided for the .TRACE command:

"The .TRACE command continues execution of a program that has stopped
because of an error, a stop statement, or a keyboard interrupt."

This definition was located in

IDL API Reference Guides > IDL Reference Guide > Part I: IDL Command
Reference > Dot Commands

This documentation is different than that which would be available in
printed form. The change from the definition you had to the new
definition occurred in IDL 4.0.1 for exactly the reason you provided.
I hope that this helps.

Based on the implementation of the .TRACE command, it is only supposed
to complete executing the code. I was able to get the code to
complete as expected. It might be helpful if a verbose keyword was
added to the .TRACE command so that each line of code was output prior
to execution.

Best Regards,

Brandon

Report message to a moderator

[Message index]

		Re: .trace not working? By: BLemire@ittvis.com on Sat, 08 August 2009 20:14
		Re: .trace not working? By: Jeremy Bailin on Sat, 08 August 2009 19:19
		Re: .trace not working? By: penteado on Fri, 07 August 2009 20:06
		Re: .trace not working? By: David Fanning on Fri, 07 August 2009 13:36
		Re: .trace not working? By: JDS on Fri, 07 August 2009 13:11
		Re: .trace not working? By: penteado on Fri, 07 August 2009 10:44
		Re: .trace not working? By: David Fanning on Thu, 06 August 2009 18:40
		Re: .trace not working? By: jkj on Thu, 06 August 2009 17:52
		Re: .trace not working? By: Bruce Bowler on Thu, 06 August 2009 06:44
		Re: .trace not working? By: David Fanning on Thu, 06 August 2009 05:18
		Re: .trace not working? By: Bruce Bowler on Thu, 06 August 2009 05:13
		Re: .trace not working? By: Michael Galloy on Wed, 05 August 2009 17:39
		Re: .trace not working? By: BLemire@ittvis.com on Wed, 05 August 2009 14:16
		Re: .trace not working? By: JDS on Mon, 10 August 2009 10:33

Previous Topic:	Re: Plot multiple axes with log and linear scales
Next Topic:	3D UserSym?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 09:51:08 PDT 2025

Total time taken to generate the page: 0.96119 seconds