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

Home » Public Forums » archive » Using BREAKPOINT
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Using BREAKPOINT [message #4649] Mon, 26 June 1995 00:00
Russ Welti is currently offline  Russ Welti
Messages: 27
Registered: October 1994
Junior Member
I hate BREAKPOINT. Every time I really need to use it it
refuses to work, saying it can't find source code corresponding
to the given line number.

% BREAKPOINT: Unable to find code corresponding to given source line.

I realize that IF/ELSEs and DOs etc. often compile as one line even
though they look like several in the file. But even if I increase
or decrease the line number, step by step through an entire range of
line numbers, it usually refuses to set a breakpoint no matter what!

For example, I will say:

breakpoint,'find_lanes.pro',88
% BREAKPOINT: Unable to find code corresponding to given source line.

breakpoint,'find_lanes.pro',89
BREAKPOINT: Unable to find code corresponding to given source line.

breakpoint,'find_lanes.pro',90 All of these fail the same way.
breakpoint,'find_lanes.pro',91
breakpoint,'find_lanes.pro',92
etc etc etc.

BTW, Lines 88 and 89 of the file are simple statements:

top_mdn=mdn*(1.0+(mdnpcnt*0.01))
bot_mdn=mdn*(1.0-(mdnpcnt*0.01))

Occasionally BREAKPOINT has worked for me, but it is really a
unreliable way to have to work, and the supposed improvements to
it for 4.0 are undiscernable. I simply do not use it; it wastes
my time.

Does anyone know why it would refuse to find source code for a
given line? Does it matter if I am already stopped in the same
file and routine as I am trying to place a breakpoint in?

What gives?

PS:
Since <filename> argument is listed as an optional argument,
wouldn't it be nice if it would default to the current file/routine
when it is absent, but NO, it doesn't. The only times the
filename string argument is optional is when you are CLEARing or LISTing
breakpoints! OOOeee isn't that a huge timesaver!

/
Russ Welti /-\
(c-g)
University of Washington \-/
Molecular Biotechnology /
PO Box 352145 /-\
Seattle, WA 98195 (a-t)
rwelti@u.washington.edu \-/
(206) 685 3840 voice (206) 685 7344 FAX /
http://chroma.mbt.washington.edu/graphics/gif/russ.gif
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Implicit None for IDL???
Next Topic: slow output to the log window under Mac OS

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

Current Time: Sat Oct 11 08:41:36 PDT 2025

Total time taken to generate the page: 1.03972 seconds