comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Interactive Debugging Tools
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: Interactive Debugging Tools [message #67152] Fri, 03 July 2009 16:45
dosfun is currently offline  dosfun
Messages: 14
Registered: February 2009
Junior Member
On 7月3日, 上午2时54分, David Fanning <n...@dfanning.com> wrote:
> Folks,
>
> I've been debugging a program this week that uses a large
> image cube. I peel one image after the other off the cube
> because I can't load the whole cube into memory at once.
>
> But that's neither here nor there. The point is,
> there is a problem with some of the image data and
> I've been trying to track it down. I have some very
> nice tools for interactively looking at images and
> their values at specific locations (I am thinking
> in particular of ImgWin.) The problem is, I can't use
> ImgWin to look at my image data when I am stopped
> inside my program, because as a widget program, ImgWin
> needs access to the command interpreter at the main
> IDL level. A dilemma, as they say.
>
> If I could only get my image data back to the IDL
> main IDL command level where I could look at it.
> Well, now I can. I wrote a new Coyote Library program
> this morning, named SaveToMain. I can use it to export
> any IDL variable from within any IDL procedure or function
> back to the main IDL level:
>
> IDL> SaveToMain, thisImage
>
> If I call the program as above, the variable is
> exported to the main level with the same name as it
> has in the local procedure or function. If I wish
> to give it a new name, I just do this:
>
> IDL> SaveToMain, thisImage, 'problemImage'
>
> This allows me to be in my stopped code somewhere. Find a
> variable I want to look at, export it back to the main level
> of IDL, type RETALL to return to the main IDL level, and
> use my interactive widget tools to further investigate the
> variable. I just find this extremely useful. Maybe you
> will, too.
>
> http://www.dfanning.com/programs/savetomain.pro
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Coyote's Guide to IDL Programming (www.dfanning.com)
> Sepore ma de ni thui. ("Perhaps thou speakest truth.")

Very useful tool, make debugging easier and more interesting.
Re: Interactive Debugging Tools [message #67154 is a reply to message #67152] Fri, 03 July 2009 06:57 Go to previous message
vino is currently offline  vino
Messages: 36
Registered: March 2008
Member
On Jul 2, 9:25 pm, pp <pp.pente...@gmail.com> wrote:
> Very nice! No more adding pointers to be passed around through all the
> levels, or using save to keep a copy of everything in scope.
>
> Thanks.

Wow!! Thank you for this wonderful tool..I remember all the times that
i save the variable to have a look at it later....
Re: Interactive Debugging Tools [message #67159 is a reply to message #67154] Thu, 02 July 2009 13:25 Go to previous message
penteado is currently offline  penteado
Messages: 866
Registered: February 2018
Senior Member
Administrator
Very nice! No more adding pointers to be passed around through all the
levels, or using save to keep a copy of everything in scope.

Thanks.
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: In catalyst, how do I decide which object need to be destroyed by hand?
Next Topic: nike clothing,nike shoes,online store,http://www.maidi2008.net air Jordan Shoes,Nike Air Jordans, Air Force Ones,Retro Air Jordan, Bape Hoodies,Bape shoes-Tencent Traveler|Jordan Shoes,Nike Air Jordans, Air Force Ones,Retro Air Jordan, Bape Hood

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:39:33 PDT 2025

Total time taken to generate the page: 0.00899 seconds