Lines Matching +full:shared +full:- +full:memory

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,
26 data elements within the new object can be obtained from the objects' memory
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
174 The new object \fIopath\fR is constructed from the current memory contents of
179 when processing a dynamic executable, any allocated memory that follows the end
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
235 \fBa.out\fR, can be used to create a new shared object from one of the dynamic
251 The new shared object \fIopath\fR is fixed to the address of the mapped
253 relocations are applied to this new shared object, which will reduce its
284 Using a dumped shared object with applied relocations as an applications
286 the application that produced the dumped image. Dumping shared objects, and the
318          * dump the dynamic executables memory image.
351 required for the correct initialization of its shared object dependencies.
368 re-initialization. For example, if a data item contains a file descriptor, a
369 variable returned from a shared object, or some other external data, and this
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
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.
440 When a shared object is dumped, and relocations are applied which are
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