|
|
HP-UX Reference > Eelf_xlate(3E)HP-UX 11i Version 2: December 2007 Update |
|
NAMEelf32_xlatetof, elf32_xlatetom, elf64_xlatetof, elf64_xlatetom — class-dependent data translation for elf32 and elf64 files, respectively SYNOPSIScc [flag... ] file... -lelf [library] ... #include <libelf.h> Elf_Data *elf32_xlatetof(Elf_Data *dst, const Elf_Data *src, unsigned encode); Elf_Data *elf32_xlatetom(Elf_Data *dst, const Elf_Data *src, unsigned encode); Elf_Data *elf64_xlatetof(Elf_Data *dst, const Elf_Data *src, unsigned encode); Elf_Data *elf64_xlatetom(Elf_Data *dst, const Elf_Data *src, unsigned encode); DESCRIPTIONelf32_xlatetom translates various data structures from their 32-bit class file representations to their memory representations; elf64_xlatetom translates various data structures from their 64-bit class file representations to their memory representations; elf32_xlatetof and elf64_xlatetof provide the inverse. This conversion is particularly important for cross development environments. src is a pointer to the source buffer that holds the original data; dst is a pointer to a destination buffer that will hold the translated copy. encode gives the byte encoding in which the file objects are (to be) represented and must have one of the encoding values defined for the ELF header's e_ident[EI_DATA] entry (see elf_getident(3E)). If the data can be translated, the functions return dst. Otherwise, they return null because an error occurred, such as incompatible types, destination buffer overflow, and so forth. elf_getdata(3E) describes the Elf_Data descriptor, which the translation routines use as follows.
Translation routines allow the source and destination buffers to coincide. That is, dst->d_buf may equal src->d_buf. Other cases where the source and destination buffers overlap give undefined behavior. For elf32 files:
For elf64 files:
``Translating'' buffers of type ELF_T_BYTE does not change the byte order. |
|