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

Home » Public Forums » archive » Re: .trace not working?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: .trace not working? [message #67582 is a reply to message #67581] Fri, 07 August 2009 13:11 Go to previous messageGo to previous message
JDS is currently offline  JDS
Messages: 94
Registered: March 2009
Member
> And yet I still frequently see people using just the command line,
> editing source files in vi or emacs.

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?
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Plot multiple axes with log and linear scales
Next Topic: 3D UserSym?

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

Current Time: Fri Oct 10 03:02:24 PDT 2025

Total time taken to generate the page: 0.96386 seconds