• Subject: Imported pointer restrictions? -Reply
  • From: David Morris <dmorris@xxxxxxxxxxxxx>
  • Date: Thu, 13 Nov 1997 10:21:30 -0700

Found out what the problem was.  It appears DEBUG is the problem.  
It is really irritating that there are so many undocumented "features" 
in the debugger.

>>> David Morris <dmorris@plumcreek.com> 10/31 1:07 pm >>>
>I have run into a problem using pointers.  I receive no error, just a null 
>pointer when trying to set a pointer in the following case:

>Declare a pointer "P1" in service program(s) "A" as exportable.
>Declare a variable as based on "P1".

>In service program "B" - 
>Declare a pointer "P2" based on pointer "P3".
>Activate service program "A" using an API.
>Set "P3" by retrieving exported pointer "P1" using an API.
>Set "P2" using ALLOC or %ADDR.

>I receive no error and "P2" remains null.

The pointer is not null, the debugger just says it is.  
This situation happens when you try to display a variable in another 
activated module.  It displays properly (with 80000000 0000000 in front) 
if I use:

EVAL P3 :X 16

I get *NULL if I use this:
EVAL P2

This happens in other cases.  I should at least get CPF8e28:
"Variable not available to display" 

David Morris
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].