Re: iSeries Debugger Gone Wild

As Ken has said, the mostly likely culprit is the object and source being
out of sync. I have this happen from time to time. Usually I just make
sure I recompile the object from that source member and then refresh the
Service Entry Point. One note, if you recompile an object the old service
entry point will no longer work. YOU HAVE TO REFRESH. It won't even kick
off. So if you recompiled and the service entry point still kicked off
then you might want to look at the library you specified in the SEP and
make sure that is actually the library where your object resides.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



"Tarr, Kenneth" <Kenneth.Tarr@xxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
08/26/2010 02:05 PM
Please respond to
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] iSeries Debugger Gone Wild






I had similar problems with WDSC; it may have to do with the source you're
viewing is not in sync with the object you're running. Unfortunately I'm
on RDP V7.6 so I don't exactly recall where you would change this setting,
but I believe when you are working with your debug configuration, you want
to change the source lookup path. You could delete it, in which case it
will prompt you for what source you want to view. Other things would be
to clear your cache (although I don't think this will impact it).

Ken Tarr
Associated Banc Corp
Green Bay Service Center, Mail Stop 7055
2870 Holmgren Way, Green Bay, WI 54304
www.associatedbank.com


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Larenzo Alexander
Sent: Thursday, August 26, 2010 12:49 PM
To: Rational Developer for IBM i / Websphere Development Studio Clientfor
System i & iSeries
Subject: [WDSCI-L] iSeries Debugger Gone Wild

I'm using WDSC 7 and working with the iSeries Debugger. Most of the time
it works fine but sometimes it appears to be going wild. When I step
with F5, the debug line is jumping to unpredictable areas in my source
code. I was thinking maybe it had to do with me making changes to the
source code and recompiling. So I tried refreshing the service entry
point and that didn't work, I tried removing the service entry point and
added another one and that didn't work. I closed debugger and WDSC and
reopened it and that didn't work. I even rebooted my PC and stop and
started the Debug Remote server and that didn't work.



If anyone has any suggesting on what to try next or what causes this, I
would greatly appreciated it. I guess back to Green Screen debugger I
go, for now. J



Thanks