Re: Can not get breakpoints set in RSE source to work-resolved -- WDSCI-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: [WDSCI-L] Can not get breakpoints set in RSE source to work-resolved
From: Dave Murvin <davem@xxxxxxxx>
Date: Thu, 30 Sep 2004 09:51:11 -0700
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

Vadim,

Thanks for the explanation. Since I sometimes like to see some of the values of variables that are not in the source (such as in copy members), I have been in the habit of compiling all programs with the *LISTING view since this gives me the maximum visibility. Since this always seemed to work in the regular green screen debugger, I never gave it a thought. I will change my debug view to *SOURCE or *ALL.

At 09:06 AM 9/27/2004, you wrote:

Now, if you compiled your program only with *LISTING view, debugger will
automatically switch to that
*LISTING view, and none of the 'source file breakpoints' will be installed
for that debug session.


Dave Murvin
DRM Enterprises, Inc.

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