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

-----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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.