| Re: Seeing Source w/ Debugger [message #2391 is a reply to message #2389] |
Fri, 24 June 1994 06:02   |
robijn
Messages: 18
Registered: June 1994
|
Junior Member |
|
|
In article <CrvKsA.Lro@hpl.hp.com>, Peter Webb <peter@hpl.hp.com> wrote:
>
> My biggest complaint is that the debugger can only find routines that
> are in the directory in which IDL (or PV-WAVE for that matter, they both
> have the same problem) is started.
That is not true, although I must admit that the filename argument
interpretation of BREAKPOINT could be improved. It all depends how
you compiled the routine. If you type:
.run [path/]func[.pro]
([] indicate optional parts) and the file [path/]func.pro exists, you
should use that name in BREAKPOINT. Otherwise you should prepend the
directory where the file resides _exactly_ as that directory appears
in the !PATH variable.
It would be a good idea to let BREAKPOINT search the path in the same
way as .RUN does. Better still, make the path-search code available as
separate routine as well. I wrote an IDL routine called 'which' that
does the trick for DOS and Unix systems.
If you place 'which.pro' somewhere in the IDL path, you can set your
breakpoints as:
breakpoint, which ([path/]func.pro), ...
Frank
--
_____ ____
/ / / Frank Robijn Internet: Robijn@Strw.LeidenUniv.NL
/___ /___/ Sterrewacht Leiden Bitnet: Robijn@HLERUL51
/ / \ Phone (31) 71 275841 Local: Robijn@HL628
/ / \ Fax : (31) 71 275819 Snail: P.O.Box 9513, 2300 RA Leiden,
The Netherlands
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
