|
A follow up...when in debug view I can click on the line and select Switch View. From here I can select *SOURCE or *STATEMENT. When *SOURCE is selected, it points to the wrong line. When *STATEMENT is selected, it shows the right line, but does not show the actual code (just the statement number). So is there something set up wrong that it's pointing to the source incorrectly? I've searched for other copies of the source and the only one is in my library which I have it pointing to...the same copy that is now compiled and running in debug.
Ken
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Tarr, Kenneth
Sent: Monday, February 22, 2010 11:11 AM
To: 'Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries'
Subject: [WDSCI-L] Debug not in sync (WDSC 7.0.0.8)
I am having a problem with Debug not in sync with the line numbers. Since a couple of days ago I have not been able to use Debug to debug my application. It shows a completely different line number from the source than what is actually being executed.
Here's what I have tried so far:
-- Recompiled the application
-- Cleared the cache (there are two locations where this can be done)
-- Changed to a different workspace
-- Clicked the Outline view to refresh the outline
No matter what I do, even when new lines are added or existing lines in the program are removed, it doesn't sync up (and keeps going to the same line number when I press F5 or F6 the first time when the application begins).
I've even had it point to the source in two locations; one on the iSeries, and one on my hard drive. Still comes to the same line numbers which are not the actual lines being executed.
As an Amazon Associate we earn from qualifying purchases.
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.