×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Rory Hewitt wrote:
The user space *doesn't* know that it's a pointer - as you pointed out, it's
up to the programs that reference that data to specify that it's a pointer.
However, the difference between a user space and a data area/data queue etc.
is that you *can* *technically* store a pointer inside a user space, because
the user space can also store the tags etc.
Before I put this completely to bed ... since I can send a pointer to
another job in a user space ... is there some way the system protects
itself from a pointer in a job being set to an arbitrary location (that
may actually exist in another job)?
When a pointer is passed via a user space, is it tagged in some way to
indicate that the memory location is explicitly being shared?
One other thing ... when you do pass a pointer from one job to another
via user space, is the memory the pointer refers to as writable as any
other memory? So, could program A pass a pointer to space in it's job
to program B, and program B could then overwrite storage in program A's job?
david
This mailing list archive is Copyright 1997-2025 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.
midrange.com
