Re: Memory Leaks in RPG

James Lampert wrote:

But the job being peeked at has to actually send the peeking job the pointer.

Who's to say where the pointer came from? I could create a pointer by simply doing ...

newPointer = %addr(existingPointer) + 1000000000000;

Not a very meaningful example, but I think you get my point(er).

Besides, isn't that what happens every time a socket server spawns off a child server job? If I remember right, the child server job sends the spawning job a request for the socket, and the job ID to hand it off to, and the spawning job sends back a pointer to the socket.

I think you're referring to a socket descriptor ... which has to be explicitly given by the sending program and then taken by the receiving program.

Seems to me that service jobs are a far bigger security risk.

You mean STRSRVJOB? That could be a security risk ... but you need to have sufficient authority to use it, and I don't think it's very meaningful to use within an application.

david