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 #67580 is a reply to message #67578]

Fri, 07 August 2009 20:06

penteado
Messages: 866
Registered: February 2018

Senior Member
Administrator

On Aug 7, 5:11 pm, JDS <jdtsmith.nos...@yahoo.com> wrote:
> Ho-now. In Emacs with IDLWAVE I can:
>
> 1) report on the call stack at a stopped location.
> 2) use single keystrokes to examine variables (not just print, but
> view structure fields, see widget dimensions etc., or other things you
> can dream up and easily configure). I can also drag out or use
> shortcuts to examine any arbitrary expressions in the code (like '(x +
> y^z)').
> 3) move up and down through the call stack, examining variables or
> expressions in any parent scope (in practice I just do this rather
> than read the traceback).
> 4) trivially set, remove, or alter breakpoints, including conditional
> and repeat breakpoints
> 5) continue, step, stop, continue to the line at the cursor point,
> continue up and out of the enclosing block (for loop, etc.)
>
> So basically (as far as I can tell) every debugging option in the
> Workbench, and a bit more. Not as much clicking, but for some that's
> an advantage. Did I mention it's been doing this for about 10
> years?

Ok. I did not know one could do that much in IDL with Emacs, and I am
also impressed that it has been the case for so long. I have for some
time intended to examine Emacs in more detail, this encourages me to
do it sooner.

However, the people I was referring to, which I frequently see, do not
use such features, they only edit source files as one would do in vi
or any other simple text editor, run things in IDL in a command line,
and fill the code with prints when trying to debug, with a lot of
avoidable suffering.

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).

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 12:44:05 PDT 2025

Total time taken to generate the page: 1.08810 seconds