| .trace not working? [message #67607] |
Wed, 05 August 2009 13:13  |
Bruce Bowler
Messages: 128
Registered: September 1998
|
Senior Member |
|
|
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
bbowler@bigelow.org |
+-------------------+--------------------------------------- ------------+
|
|
|
|
| Re: .trace not working? [message #67704 is a reply to message #67607] |
Tue, 11 August 2009 09:23  |
jschwab@gmail.com
Messages: 30
Registered: December 2006
|
Member |
|
|
> +++++++++++++++++++++++++++
> Informal survey:
>
> ( ) IDLWHO?
> ( ) I recently switched from IDLWAVE to the Workbench.
> ( ) I use both IDLWAVE and Workbench, depending on the setting/task/
> context.
> (X) You can pry IDLWAVE from my cold, dead hands.
> +++++++++++++++++++++++++++
Thanks for your work on it!
Josiah
|
|
|
|
| Re: .trace not working? [message #67713 is a reply to message #67607] |
Mon, 10 August 2009 12:35 |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
JDS wrote:
>> Not to try to make it a contest, just to inform more to others (as you
>> have informed me of what can be done in Emacs): in the workbench
>> editor it is also possible to see a routine's arguments when you park
>> the cursor over its name (even when it is user-defined), open its
>> help, and jump to its definition (even when in another file). There is
>> help on method names and structure fields when typing them in the
>> editor and command line, and there are browsers for the command
>> history, profiler results, and routines defined in a file (the outline
>> view).
>
> I haven't really used the workbench much, so this is interesting to
> know. Routine info is in IDLWAVE for system-distributed, compiled,
> buffer-loaded, and scanned routines. You can also pre-scan all your
> local routines, and many libraries (like Fanning, NASAlib, etc.) ship
> pre-scanned. Which means you can get help on a routine even before
> IDL has compiled it, even if you can't quite remember its name, even
> if the shell isn't running (e.g. no license available). Context-
> sensitive help is there too. You can also jump directly to help on
> individual keywords, saving you scrolling down to find them. You can
> get help on structure tags for structures defined elsewhere in your
> code (like 'state'), object fields, control statements, system
> variables, etc., etc.
>
> That said, completion is probably the one area where IDLWAVE still
> (AFAIK) exceeds the Workbench: your can complete routine names,
> keywords, reserved words, system variables, structure members, object
> methods, filenames on disk, etc., all with the (alt-)tab key. I find
> myself hitting tab and groaning constantly when I've used the
> Workbench. But, as David says, admittedly the learning curve is
> steeper compared to the point-and-click browsers. Actually, it's not
> that it's really that steep, it's just that it sits near the top of
> the giant Emacs learning peak.
>
> All of this brings up an
>
> +++++++++++++++++++++++++++
> Informal survey:
>
> ( ) IDLWHO?
> ( ) I recently switched from IDLWAVE to the Workbench.
> ( ) I use both IDLWAVE and Workbench, depending on the setting/task/
> context.
> ( ) You can pry IDLWAVE from my cold, dead hands.
> +++++++++++++++++++++++++++
>
> For the record, I don't mind in the least if people do switch to the
> WB. It's the first really featureful IDE they've offered.
>
> JD
Really, none of the above. For debugging, I will occasionally start up
the Workbench if it looks like it's going to be difficult figuring out
what is wrong. For most stuff, just a command line and a separate editor
(TextMate with the IDL bundle).
Mike
--
www.michaelgalloy.com
Associate Research Scientist
Tech-X Corporation
|
|
|
|
| Re: .trace not working? [message #67715 is a reply to message #67607] |
Mon, 10 August 2009 11:49 |
Matt[2]
Messages: 69
Registered: March 2007
|
Member |
|
|
JDS <jdtsmith.nospam@yahoo.com> writes:
> +++++++++++++++++++++++++++
> Informal survey:
>
> ( ) IDLWHO?
> ( ) I recently switched from IDLWAVE to the Workbench.
> ( ) I use both IDLWAVE and Workbench, depending on the setting/task/context.
> ( X ) You can pry IDLWAVE from my cold, dead hands.
Or as soon as eclipse has full integration with emacs.
Matt
--
Matthew Savoie - Scientific Programmer
National Snow and Ice Data Center
(303) 735-0785 http://nsidc.org
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
