Very Computer

1. Solaris Shared Memory, Shared Libraries and Heap

I have a question about management of the virtual address space for
a process in Solaris.

When it comes to allocating the address space amongst dynamically
varying space requirements of heap, shared memory and shared libraries
what policy does Solaris use?

Are there distinct ranges in the address space reserved for
heap, shared memory and libraries, or can say the space
required by each be split up amongst non-contiguous blocks?

The question was sparked by the existence of the SHMBASE
environment variable used by Informix to set the
base address of shared memory segments created by
Informix.

I thought that the shmaddr argument to shmat was only a hint
to the OS, and not a explicit command. Having users specify
this seems a horribly non-portable and overall bad idea.

Where would one obtain information about the right/valid base
address to explicitly specify anyway?

Saurabh

--

2. REXEC error

3. Shared Library/Shared Memory

4. Help parsing lspci

5. Will strip(debug shared library) == nodebug shared library ?

6. Two modems on one machine?

7. Help with building shared libraries with dependencies on other shared libraries

8. javac for freeBSD

9. Question: Inclusion of shared libraries during linking of shared libraries

10. Shared library loading shared library.

11. Need a Shared Library Guru: beyond simple shared library question

12. When is a shared library not a shared library?

13. Solaris 10: Increasing the process data space; shared memory segments & intimate shared memory problems