comp.lang.idl-pvwave archive: archive » IDL Workbench Ignoring Breakpoints

Home » Public Forums » archive » IDL Workbench Ignoring Breakpoints

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

Re: IDL Workbench Ignoring Breakpoints [message #60114 is a reply to message #60064]

Wed, 30 April 2008 11:15

Jean-Paul Davis
Messages: 17
Registered: March 1998

Junior Member

I wonder if this is related to a bug I've reported where, if you use
the Run Project command (with Project Properties -> Run Command set to
the desired source file), breakpoints work but cause strange errors
such as the following:

% Breakpoint at: V7TEST 13
% CD: String expression required in this context:
_IDLDT$_RUN$_CURRENT_DIR.
% Execution halted at: V7TEST 13
% $MAIN$
% Identifiers can only be added or deleted at the main level:
_IDLDT$_RUN$_CURRENT_DIR.
% Execution halted at: V7TEST 13
% $MAIN$

They work fine (without error) as long as I don't use Run Project,
instead ensuring that my main source file is in the top editor tab and
using Run <filename>. A minor annoyance since I usually don't even
need the top-level source file open while I'm working on the code.

The bug is CR 50591 in ITT's system, and a fix is expected for version
7.1 in early 2009. Maybe it's not related, but I thought it useful to
put this information out there for others looking up breakpoint
problems.

Jean-Paul

Report message to a moderator

[Message index]

		IDL Workbench Ignoring Breakpoints By: David Fanning on Thu, 24 April 2008 13:44
		Re: IDL Workbench Ignoring Breakpoints By: Jean-Paul Davis on Wed, 30 April 2008 11:15

Previous Topic:	Empirical Orthogonal Function analysis in IDL
Next Topic:	Embedding GUI into a computational procedure

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Oct 11 21:06:58 PDT 2025

Total time taken to generate the page: 0.48177 seconds