|
Ok, here I have another example.list
I start my program and step into the beginning of the sub procedure
where a dspf field will be initialised. I check that its value is
blanc. I put a break point on the instruction after the field is
initialised. The program stops at the breakpoint and not at the line
where the field is initialised.
I wonder if this is a bug that we have not fixed?
-----Message d'origine-------
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Vern Hamberg
Envoyé : jeudi 8 octobre 2009 23:03
À : Midrange Systems Technical Discussion
Objet : Re: STRDBG problem with WATCH
David
If it's truly called by reference, then a change in the
called procedure will be reflected to the caller. But you did
not give us the prototype - Maybe there is something there ti
give a hint.
Vern
David FOXWELL wrote:
Hi Vern,and is passed by reference.
It's local, but it always has the same name in all modules,
Vern Hamberg
-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de
WDSc debuggerEnvoyé : jeudi 8 octobre 2009 14:43 À : Midrange Systems Technical
Discussion Objet : Re: STRDBG problem with WATCH
Is errorMessage a local variable or a global one?
Vern
David FOXWELL wrote:
Hi,debugger for a long time. It's probably something I'm not
I have this problem with the watch function on the iseries
understanding correctly. As I don't have access to the
not blankso stuck with STRDBG, I'm asking here.
Here's an example :errorMessage ) in module A, I notice that errorMessage is
With the program stopped at a break point on a CALLP (
arrive at mybefore the call. So I do F17(watch) on errorMessage and
F12 to continue.
The program breaks automatically in module B whereerrorMessage is initialized to blanks. F12 again and I
please takeCALLP break point again, with the same message in errorMessage.
Whats occurring?--
Thanks!
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
--a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list To post a message email:
MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change
list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting,
please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-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.