RE: Memory Leaks in RPG (was: Is RPG 'DEAD")

if the job that allocated the memory ends, the pointer will point to
unreserved memory, and produce the same sorts of "unpredictable

results"

that you'd have with a buffer overflow

Interesting. "unpredictable results" is not the same as "tried to refer
to an object that does not exist" :) So I've still got access to that
memory space? And whatever ends up there next?

If you truly want to have a pointer ot memory that's shared across
multiple jobs, there are two much safer ways:

Agreed. However, looking at the api docs (v6r1) there's no mention of
what happens if you don't detatch and then delete the shared memory
space. If I allocate shared memory and then my job ends, it would seem
the memory is still allocated. Hence, a cross-job memory leak.

-Walden