× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I had this happen to me once. I had an old version of the source in
iseries project navigator and the debug viewer was finding that one
first. I deleted the old member and that fixed it.

Roger

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Larenzo Alexander
Sent: Thursday, August 26, 2010 1:49 PM
To: Rational Developer for IBM i / Websphere Development Studio
ClientforSystem 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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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.