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



Xuan,

The listing view works correctly, and I confirmed that the source being
displayed is the source the module was compiled from.

I've sent you some screen caps in an OFFLIST email.

Couple of things I noticed:
1) Not every module I debug has this problem, only one in particular
that I noticed so far.
2) With a SEP set on a particular procedure in this module, when the
debugger starts, the properties box of the thread(?) shows "Statement
63200" which is the statement number that contains the beginning p-spec
of the procedure.  With the listing view, the debug cursor is on this
statement.  With the source view, the debug cursor is shown on statement
61800.  (Note that I have option(*SRCSTMT) specified in this and every
other module)

Thank you,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx 
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Xuan Chen
Sent: Friday, October 13, 2006 9:44 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Debugger not stepping through code correctly

Charles,

Could you please switch to *LISTING view to see if the debugger steps
through the code correctly?  You could do that by right click 
on the source
editor area, and choose Switch View --> Show *LISTING.

If your *LISTING view works fine, please check if the source 
displayed is
the right source where the program compiled from.  To check 
this, please
follow the steps below:

. Switch back to your source view.
.  Bring up the Properties view by Window -> Show View -> Other ->
Properties.
. Switch to the Program view of the debug perspective, and expand your
program until you could see the source of your module.
. Click on the source so that you could see its full path in 
the Properties
view.
. Flyover your mouse on the tab of the editor which displays 
your source
view to see its full path.  Make sure it matches to the path 
of the source
shown on the Properties view.

Please let me know the result of your checking.  Thanks.

Regards,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx




                                                              
             
             "Wilt, Charles"                                  
             
             <CWilt@xxxxxxxxxx                                
             
             om>                                              
          To 
             Sent by:                  "Websphere Development 
Studio       
             wdsci-l-bounces@m         Client for iSeries"    
             
             idrange.com               <wdsci-l@xxxxxxxxxxxx> 
             
                                                              
          cc 
                                                              
             
             10/13/2006 08:23                                 
     Subject 
             AM                        [WDSCI-L] Debugger not 
stepping     
                                       through code correctly 
             
                                                              
             
             Please respond to                                
             
                 Websphere                                    
             
                Development                                   
             
             Studio Client for                                
             
                  iSeries                                     
             
             <wdsci-l@midrange                                
             
                   .com>                                      
             
                                                              
             
                                                              
             




I was working from home last night trying to debug some code and was
having difficulty with the debugger.

The debugger didn't seem to be stepping through the code properly.  By
that I mean that the highlighted line didn't seem to be the line
actually be executed.

I recompiled my modules and updated my service programs, but 
that didn't
seem to have an effect.

Note that my modules were compiled with DBGVIEW(*ALL).

I didn't think to check, but I'm pretty sure that the 
optimization level
was set to *NONE.

Using the verify connection turned up one missing PTF, which 
was related
to debugging, but whose APAR didn't seem to mention the problem I'm
having.  Never less, I've asked that the PTF be applied.

My WDSC client is fully patch with iFix2 (6.1.0.2<?>)

The iSeries I was working with is running v5r3.

Does anyone have any advice on how to handle this problem?  
Any steps to
take that might fix the problem? Clearing cached files for instance?


I really don't want to be stuck with STRDBG while working 
this weekend.


Thank you,

Charles Wilt
--


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


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

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.