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 #67589 is a reply to message #67588]

Thu, 06 August 2009 17:52

jkj
Messages: 48
Registered: April 2007

Member

On Aug 6, 8:44 am, Bruce Bowler <bbow...@bigelow.org> wrote:
> On Thu, 06 Aug 2009 06:18:48 -0600, David Fanning wrote:
>> Bruce Bowler writes:
>
>>> Is there a *SUPPORTED* (hell, at this point I'd take unsupported) way
>>> to TRACE the execution of a routine?
>
>> Lots of PRINT statements! ;-)
>
>> Cheers,
>
>> David
>
> I figured you'd say that :-). There are about 1000 lines of code (lots
> of different routines) where my procedure could be stopping. I'd really
> rather not add another 1000 print statements :-)
>
> Oh well... sore fingers, here I come.
>
> Bruce
>
> --
> +-------------------+--------------------------------------- ------------+
> Bruce Bowler | Patriotism is the last refuge of a scoundrel. -
> 1.207.633.9600 | Samuel Adams
> bbow...@bigelow.org |
> +-------------------+--------------------------------------- ------------+

I have always used ".cont" to resume execution and when I want to know
the nesting of calls by which I arrived at the given stop I enter
"blah", giving me a traceable path up through the calling code.

It certainly sounds like ".trace" is exactly equivalent to ".continue"
but nobody wants to address it clearly - weird. I can't imagine why
IDL supplies ".trace" and ".continue" without giving a clear reason
about the differences - .trace is clearly misnamed if all it does is
continue execution... must be something more with a bit deeper
digging, but I'm not getting my shovel out for that one.

For object code I create a function call for each object
"::get_hack_val" that returns a '1' when I want to trace execution
paths, so every routine checks "->get_hack_val()" and if it returns
"1" then a print of the routine's name and any other helpful
information (status of keywords, for example) is printed.

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: Sat Oct 11 06:41:17 PDT 2025

Total time taken to generate the page: 1.20011 seconds