comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » Debugging overload

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Debugging overload [message #88609 is a reply to message #88607]

Fri, 16 May 2014 17:19

Michael Galloy
Messages: 1114
Registered: April 2006

Senior Member

On 5/16/14, 3:58 PM, Chris Torrence wrote:
> Can't you just do F6 or hit the Step Over button instead? Other than
> the fact that you can't see the pro code, I don't see much difference
> between this and stepping into something like "dist.pro". Also, even
> if you do accidentally step into a save file, you can hit F7 (Step
> Out) to immediately get back out.
>
> Finally, in IDL 8.3.1 we are going to report line numbers for save
> files. This doesn't do you any good in this case (since you don't
> have the pro code) but for your own save files you might actually
> want to step through them as a save file but see the line numbers.

So you are associating line numbers with byte code? What about a line
profiler? i.e., time spent on particular lines of code instead of just
in routines.

Mike
--
Michael Galloy
www.michaelgalloy.com
Modern IDL: A Guide to IDL Programming (http://modernidl.idldev.com)
Research Mathematician
Tech-X Corporation

Report message to a moderator

[Message index]

		Debugging overload By: Fabzi on Fri, 16 May 2014 08:20
		Re: Debugging overload By: Jim Pendleton on Fri, 16 May 2014 12:44
		Re: Debugging overload By: chris_torrence@NOSPAM on Fri, 16 May 2014 14:58
		Re: Debugging overload By: Michael Galloy on Fri, 16 May 2014 17:19
		Re: Debugging overload By: Fabzi on Sat, 17 May 2014 01:54

Previous Topic:	Common block conumdrum
Next Topic:	Coyote NCDF_FILE object to read HDF

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 15:48:11 PDT 2025

Total time taken to generate the page: 0.00512 seconds