Lines Matching +full:image +full:- +full:specific

4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
8 dldump \- create a new file from a dynamic object component of the calling
24 file. Relocations can be applied to the new object to pre-bind it to other
25 dynamic objects, or fix the object to a specific memory location. In addition,
27 image as this data exists in the calling process.
36 limitations in regards to data usage can make dumping a memory image
49 into two basic types: \fInon-symbolic\fR and \fIsymbolic\fR.
52 The \fInon-symbolic\fR relocation is a simple \fIrelative\fR relocation that
69 affect the relocations that are applied to the new object. \fINon-symbolic\fR
157 location that the \fIipath\fR image is mapped within the current process.
175 the \fIipath\fR image as it exists in the calling process. This option allows
185 been applied to the \fIipath\fR memory image that do not fall into one of the
197 are not part of the dynamic objects' memory image are removed. \fBRTLD_STRIP\fR
227 Otherwise, a non-zero value is returned and more detailed diagnostic
247 .in -2
264 Use of the other relocation flags can fix specific relocations in the new
286 the application that produced the dumped image. Dumping shared objects, and the
318          * dump the dynamic executables memory image.
325 .in -2
368 re-initialization. For example, if a data item contains a file descriptor, a
371 have no meaning in the new dumped image.
377 new image will effectively be lost or invalidated within the new image. For
380 that it can be relocated when the new image is used; hence, the previous
385 Non-idempotent data initializations may prevent the use of \fBRTLD_MEMORY\fR.
386 For example, the addition of elements to a linked-list via \fBinit\fR sections
387 can result in the linked-list data being captured in the new image. Running
388 this new image may result in \fBinit\fR sections continuing to add new elements
392 this may invalidate the calling image; thus, following the call to
399 to dynamically-linked processes only. See \fILinker and Libraries Guide\fR).
412 MT-Level	MT-Safe
426 These functions are available to dynamically-linked processes only.
431 an \fBELF\fR file image. \fBNOBITS\fR sections declare memory that must be
432 created and zero-filled when the object is mapped into the runtime environment.
435 \fBELF\fR file image. This section conversion reduces the runtime
444 linker, but is not valid as input to the link-editor.
452 the runtime linker or link-editor, but can reduce the objects analysis with