| Re: Reporting routines called [message #28692] |
Sat, 05 January 2002 22:56 |
John-David T. Smith
Messages: 384
Registered: January 2000
|
Senior Member |
|
|
Pavel Romashkin wrote:
>
> From: "JD Smith" <jdsmith@astro.cornell.edu>> If you use IDLWAVE
> (http://idlwave.org), you can just insert a
>> breakpoint and navigate the call stack with C-c C-d C-Up. This is even
>> nicer, because you can see the context of each call in the code itself,
>> print variables local to that stack level, etc.
>
> For those of us deprived of the luxury of using the Wave, you can resort
> also to inserting a breakpoint in the IDL DE and look up the call stack.
> Breakpoints in DE have nice features such as conditional breaking, breaking
> on the counter, etc.
> Good luck,
> Pavel
> P.S. I am afraid I will be forever deprived of the Wave mode because I can't
> stand the Xwindows interface that I used so far :(
I share your pain, Pavel, but you might be on a collision course with XWindows
if you stay with Mac, since the OS X version of IDL due out is hosted by an X11
server. Maybe then you could give IDLWAVE a try, on a suitable snazzy-looking
Emacs of course ;) :
http://emacs-on-aqua.sourceforge.net/
JD
P.S. IDLWAVE can do conditional/repeated breaks, etc. too.
|
|
|
|
|
|
| Re: Reporting routines called [message #28696 is a reply to message #28694] |
Fri, 04 January 2002 22:03  |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
From: "JD Smith" <jdsmith@astro.cornell.edu>> If you use IDLWAVE
(http://idlwave.org), you can just insert a
> breakpoint and navigate the call stack with C-c C-d C-Up. This is even
> nicer, because you can see the context of each call in the code itself,
> print variables local to that stack level, etc.
For those of us deprived of the luxury of using the Wave, you can resort
also to inserting a breakpoint in the IDL DE and look up the call stack.
Breakpoints in DE have nice features such as conditional breaking, breaking
on the counter, etc.
Good luck,
Pavel
P.S. I am afraid I will be forever deprived of the Wave mode because I can't
stand the Xwindows interface that I used so far :(
|
|
|
|
| Re: Reporting routines called [message #28700 is a reply to message #28696] |
Fri, 04 January 2002 15:31 |
John-David T. Smith
Messages: 384
Registered: January 2000
|
Senior Member |
|
|
"Pavel A. Romashkin" wrote:
>
> One way to do this is to use the Profiler. It doesn't print them but it
> does show them.
> Pavel
>
> Gabe wrote:
>>
>> Hello,
>>
>> In IDL, is it possible to print out which routines are called during
>> execution?
>> I can print out all compiled routines using help, /routines. It would
>> be very helpful to know which of these are called in which order.
>>
>> Thanks
Or try:
help,/traceback
If you use IDLWAVE (http://idlwave.org), you can just insert a
breakpoint and navigate the call stack with C-c C-d C-Up. This is even
nicer, because you can see the context of each call in the code itself,
print variables local to that stack level, etc.
Good luck,
JD
|
|
|
|
| Re: Reporting routines called [message #28702 is a reply to message #28700] |
Fri, 04 January 2002 10:50 |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
One way to do this is to use the Profiler. It doesn't print them but it
does show them.
Pavel
Gabe wrote:
>
> Hello,
>
> In IDL, is it possible to print out which routines are called during
> execution?
> I can print out all compiled routines using help, /routines. It would
> be very helpful to know which of these are called in which order.
>
> Thanks
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
