I'm using the SEP debug.
In the Variables window there are none displayed.
And there is a message displayed. "No local variables are available for the selected stack frame"
If I right click on a variable in the debug window I get the message DBGE00004E Could not evaluate expression "variable name".
The outline does display all the variables so there seems to be some disconnect somewhere.
I am going to try and compile the source directly into the remote environment from the source there and see if that makes a difference.
----------------------------------------------------------------
PETER THOMAS
I/90 CONSULTANT - I/90 SYSTEMS
IAG LABS
Phone. +61 3 9601 8885 Ext. 38885
Mobile. +61 412 812 615
Email. peter.thomas@xxxxxxxxxx
Address. 15/181 William St Melbourne 3000
www.iag.com.au
We help make your world a safer place.
--------------------------------------------------------------
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Wednesday, 3 February 2016 2:29 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Variables values cannot be displayed in debug
On 2 February 2016 at 22:05, Peter Thomas <Peter.Thomas@xxxxxxxxxx> wrote:
I should have also added that I can't even add variables to the monitor either.
The program object has Debug Data *yes
Could it be related to the size of the program.
I'm only guessing but someone in the team has suggested that may be the cause.
Hm. I have debugged some very large programs with RDi SEP debug and
don't recall this particular issue on any version of RDi. When you
try to add the variable to a monitor, do you get a message? Variable
not found or not in scope? I'm trying to think of the issues I've
ever had with debugging and most of them come from me either trying to
debug the object in PROD with the (wrong) source in DEV, or debugging
with old source in an iProject. There's a setting that controls the
latter: Windows > Preferences > Run/Debug > IBM i Debug, Search i
Projects first for debug source. One other thought - are you doing a
SEP debug, or are you launching a debug configuration to debug a
running job? That may prod the memory of someone else on the list.
--buck
midrange.com
