Re: SEP Debug no longer working since 9.5.0.3 Fixpackinstalled

Thanks Maha. I followed your suggestions without success so I created a new workspace and this seems to have fixed the issue. I was able to debug yesterday afternoon without issue.

The problem I have now is that code assist (ctl-space) no longer seems to be working. But I'll create a new thread for that.

Thanks,

Rob

On 4/27/2016 3:50 PM, Maha Masri wrote:

Some information from our debug developer...

The preference setting (Preferences->Remote Systems->Debug->Remote Compiled
Application - Automatically stop at the first executable line of main
method) has no impact to a SEP debug session in RDi. If you set a SEP on a
program object, the debugger should stop at the entry of the program
automatically.

You can investigate the problem using the following steps:
1. Does the debugger stop when you launch other batch or interactive jobs
using the Debug As actions from RDi?
If the debugger does not stop for any program, it is likely that you have a
dangling batch or interactive job which held up the terminal. In this case
you need to terminate the dangling job.

2. If the debugger does stop for other programs using Debug As, continue to
investigate whether these programs would stop if they are debugged using
SEP.

3. If the SEP stop issue only happens with one particular program, try to
recompile it and run SEP debug again.

4. If you set the SEP on a program object and the debugger does not stop,
try setting the SEP on a procedure or module and see what happens.

Thanks,
____________________________________________________________________________
Maha Masri Project Manager
Rational Developer for i - Rational Developer for AIX and Linux - Rational
Developer for Power




From: Robert Rogerson <rrogerson@xxxxxxxxxxx>
To: Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>
Date: 04/27/2016 11:49 AM
Subject: [WDSCI-L] SEP Debug no longer working since 9.5.0.3 Fixpack
installed
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



I installed the 9.5.0.3 fix pack yesterday.

Today I was attempting to debug a program (which I had debugged
successfully prior to installing the fix pack). I use the LMi plugin
to manage/edit my source which doesn't allow adding a SEP by right
clicking on the source. So I switch to the debug perspective and
manually add the SEP. In the IBM i Service Entry Points tab I see the
program added.

Back on the green screen I call the program which delays starting as
usual. But the program runs to the first Exfmt. Then the active window
switches to RDi and in the Debug tab I see

tmp [IBM i: Incoming Remote Debug Session]

Platfor: IBM i *UNKNOWN* Connection: COMANCHE:3825

Process: 111680/RROGERSON/RROGB Program: PI1150

The above looks normal except prior to the fix pack debug stopped on the
first executable line (Preferences->Remote Systems->Debug->Remote
Compiled Application - Autmatically stop at the first executable line of
main method is CHECKED) allowing me to add breakpoints if needed. In my
case I already have break points where execution should have stopped.

But today it is not stopping and continues execution until the program
hits the Exfmt statement. As I said a process does exist but it never
stopped to allow me to do anything.

I have tried ending the three QB5 jobs, ending RDi, doing a clean, and
starting a fresh SEP and calling the program again from the green screen
but I get the same issue as mentioned above.

Does anyone have any suggestions?

Thanks,

Rob

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.