Skip Navigation Links | |
Exit Print View | |
man pages section 3: Extended Library Functions Oracle Solaris 10 8/11 Information Library |
Extended Library Functions - Part 1
Extended Library Functions - Part 2
dat_registry_add_provider(3DAT)
dat_registry_list_providers(3DAT)
dat_registry_remove_provider(3DAT)
dat_set_consumer_context(3DAT)
devid_deviceid_to_nmlist(3DEVID)
di_link_next_by_lnode(3DEVINFO)
di_link_next_by_node(3DEVINFO)
di_lnode_private_get(3DEVINFO)
di_lnode_private_set(3DEVINFO)
di_minor_private_get(3DEVINFO)
di_minor_private_set(3DEVINFO)
di_prom_prop_lookup_bytes(3DEVINFO)
di_prom_prop_lookup_ints(3DEVINFO)
di_prom_prop_lookup_strings(3DEVINFO)
di_prop_lookup_bytes(3DEVINFO)
di_prop_lookup_int64(3DEVINFO)
di_prop_lookup_strings(3DEVINFO)
DmiListComponentsByClass(3DMI)
ea_match_object_catalog(3EXACCT)
Extended Library Functions - Part 3
Extended Library Functions - Part 4
- set fill byte
cc [ flag ... ] file ... -lelf [ library ... ] #include <libelf.h> void elf_fill(int fill);
Alignment constraints for ELF files sometimes require the presence of ``holes.'' For example, if the data for one section are required to begin on an eight-byte boundary, but the preceding section is too ``short,'' the library must fill the intervening bytes. These bytes are set to the fill character. The library uses zero bytes unless the application supplies a value. See elf_getdata(3ELF) for more information about these holes.
See attributes(5) for descriptions of the following attributes:
|
elf(3ELF), elf_flagdata(3ELF), elf_getdata(3ELF), elf_update(3ELF), libelf(3LIB), attributes(5)
An application can assume control of the object file organization by setting the ELF_F_LAYOUT bit (see elf_flagdata(3ELF)). When this is done, the library does not fill holes.