|
Hi guys, I believe a similar question/issue was posted by Ewout a bit earlier on this list as well. I am not 100% sure what causes problems in individual scenarios, but let me give you a bit of an overview and hopefully this will shed some light onto the situation. One can use RSE perspective to edit source files that reside on the iSeries. In order to integrate nicely with the iSeries debugger, we allow setting what we call a 'source file breakpoints' at that time. Unfortunately, we do not really know which Program/Service Program will contain this source file at the time. Therefore, the first time user tries to set such 'source file breakpoint', WDSC will actually prompt you to provide the name of Program/Service Program. We expect this to be correct, otherwise, once debugger starts such 'non-matching' breakpoint will simply be ignored. Then, you get to compile your source into a Module and Program/Service Program. At this point, you get to specify which debug views are to be included. You can either compile with *SOURCE or *LISTING debug view (some languages allow for *ALL views). If program was compiled with the *SOURCE view, we will try to honor all the breakpoints that you set using RSE perspective editor when you start your debug session. You will notice that once breakpoint is 'installed or active' in the debug session it will have a little checkmark next to it in the Breakpoints view. Breakpoints that were not 'activated or installed' during debug session startup will have no such checkmark. 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. Hopefully this gives you an idea as to how 'source file breakpoints' can be used by the iSeries debugger. Regards, Vadim. iSeries Run-Time Analysis Tooling Dave Murvin <davem@xxxxxxxx> Sent by: To wdsci-l-bounces@m wdsci-l@xxxxxxxxxxxx idrange.com cc Subject 09/18/2004 02:28 [WDSCI-L] Can not get breakpoints PM set in RSE source to work Please respond to Websphere Development Studio Client for iSeries I have been having a hard time figuring out how/where to set breakpoints to debug a program. I was setting break points in the source module in the RSE perspective, then trying to debug the program object interactively going through the debug menu. When I selected Resume in the Debug perspective, I assumed that the program would run to the first break point I had set. Instead, the program runs to completion without stopping at any break points. What I discovered is that the Debug perspective brings up the program to be debugged in a separate pgm.listing view. When I set the break points in this listing view, the debugger stops at the break points as expected. None of the breakpoints set in the RSE source view were transferred to this pgm.listing view. What is the purpose of setting the break points in the RSE perspective view of the source if they are not recognized by the debugger? Am I missing something? I spent quite a while figuring out how to get any break points to work. It was very frustrating. I am using WDSCi 5.1.2.1 and V5R3 Thanks. Dave Murvin DRM Enterprises, Inc. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
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.