RE: Eval *string pointer variable in debugger

Yes, I don't want to have to look for the x'00' to know what my string
really looks like. This same debugger is able to display a char * in c
program just fine using eval piDataRcv :s. Not sure why it is not able
to do the same in RPG.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Thursday, June 12, 2008 2:15 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Eval *string pointer variable in debugger

Lim,

Maybe I'm missing something, but what are you trying to do that you
*can't*do with "eval piDataRcv:c 20"? Are you just trying to see the
entire string being pointed to? In which case you could obviously do
"eval piDataRcv:c 1000" and check for the first x'00.

Are you simply trying to find a 'nicer' way of seeing the based string
without any additional data beyond the end of the string?

Rory


On 6/12/08, Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:

P myProc B
D piDataRcv *
D options(*nopass :*omit :*string)
D const


On debugger command line, I'm able to do this eval piDataRcv :c 20


Does anybody know of a better way to display the value of this pointer
variable?
I tried below and debugger is not likely them
eval piDataRcv :s
eval piDataRcv :a
eval piDataRcv :u

--
This is the RPG programming on the AS400 / iSeries (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.