AW: WDSc / RDi Debugger and global variables?

["Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx>]

Hi,

STRDBG can view it, it is the WDSC-Debugger which cannot show the global
variables.
Here a simplified example or such a source:

D SESS_DS         DS                   Based(Sess_P)
D***** Bunch of subfields (and everything in a copy member)
*-------------------------------------------------------------------
P MyProc          B                    Export

D MyProc          PR
D  ParPtr                          *  

 /Free 
   Sess_P = ParPtr;
   //Use, Fill, Replace the Data structure Subfields 
 /End-Free
P                 E                      
 *--------------------------------------------------------------------
P NextProc        B                     Export 

 /Free
   //Use, Fill, Replace the global data structure Subfields
 /End-Free
P                 E
 *---------------------------------------------------------------------
P ThirdProc       B                     Export 
D ThirdProc       PR                *  
D  ParPtr                           
 /Free
   //Use Fill Replace the global data structure subfields
   Return Sess_P
 /End-Free
P                 E

Don't ask me why he write his sources in this way.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Charles Wilt
Gesendet: Tuesday, 29. September 2009 16:08
An: RPG programming on the IBM i / System i
Betreff: Re: WDSc / RDi Debugger and global variables?

Birgitta,

Honestly, I'm not following.  A code sample may help...

However, if STRDGB can view it, then WDSCi can do it too.

How do you see the value in STRDBG?

You should be able to key the same expression into "Monitor
Expression" and see the same values you see in STRDBG using the EVAL
command.

HTH,
Charles


On Tue, Sep 29, 2009 at 9:51 AM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:
> Hi Jon and Charles,
>
> thanks for answering. Until now I'm out of luck.
>
> Hovering the mouse over a global variable is not enough.
>
> My colleague works as follows:
> He passes a pointer to a procedure, than moves the pointer into another
> pointer that points to a big global data structure.
> Don't ask me why he is working in this way. This handling causes a never
> ending trouble. Pointers to the wrong data structure, pointers are not
> passed, global variables get changed by other exported procedures and with
> the next call the wrong values are in the data structure.
>
> I like the WDSC-Debugger because of the Service Entry Points that can be
> used, which is quite helpful when debugging CGI/Web Programs.
> In either way I'll continue to debug my programs (with either WDSc
Debugger
> or STRDBG).
>
> Mit freundlichen Grüßen / Best regards
>
> Birgitta Hauser
>
> "Shoot for the moon, even if you miss, you'll land among the stars." (Les
> Brown)
> "If you think education is expensive, try ignorance." (Derek Bok)
> "What is worse than training your staff and losing them? Not training them
> and keeping them!"
>
> -----Ursprüngliche Nachricht-----
> Von: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
Im
> Auftrag von Jon Paris
> Gesendet: Tuesday, 29. September 2009 13:38
> An: rpg400-l@xxxxxxxxxxxx
> Betreff: Re: WDSc / RDi Debugger and global variables?
>
> Try using the call stack Birgitta. Usually in the upper left hand pane.
>
> Highlight the stack level you want (in your case it should be one
> above the subproc entry) and that should do it. I must admit that I
> have never done it in quite the circumstances you describe (globals in
> a subproc source) so I'm not sure it will work and haven't time to
> test but ...
>
> If that doesn't work, have you tried using the "hover" method for
> viewing the variable?  i.e. just position your mouse over the variable
> name and leave it there - does that not show the value.
>
> If neither of these work then it is PMR time!
>
> P.S. This should really be on the WDSCi list if only to get the
> attention of the developers who don't watch this one.
>
>
> Jon Paris
>
> www.Partner400.com
> www.SystemiDeveloper.com
>
>
>
> On 29-Sep-09, at 4:28 AM, rpg400-l-request@xxxxxxxxxxxx wrote:
>
> > Can someone point me into the right direction, i.e. describe me how
> > to see
> > the content of the global variables within the WDSC/RDi Debugger.
> > Or do I really have to go back to STRSRVJOB and STRDBG (which is quite
> > annoying if you have to debug CGI programs)?
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.