|
|
Hachoir core 1.2 (Default branch)
09-03-2008
Hachoir is a Python library used to represent abinary file as a tree of Python objects. Eachobject has a type, a value, an address, etc. Thegoal is to be able to know the meaning of each bitin a file. Hachoir is able to open invalid ortruncated files. It only reads or computes data ondemand to minimize load times. Many field typesare predefined (integer, bit, string, etc.) andstrings with a given character set (such asISO-8859-1 or UTF-8) are supported. Addresses andsizes are stored in bits.License: GNU General Public License (GPL)Changes:|
|
core(4) Kernel Interfaces Manual core(4) NAME
core - format of core image file DESCRIPTION
The HP-UX system writes out a file containing a core image of a terminated process when certain signals are received (see signal(5) for the list of reasons). The most common causes are memory violations, illegal instructions, floating point exceptions, bus errors, and user-gen- erated quit signals. The core image file is called and is written in the process's working directory (provided it is allowed by normal access controls). A process with an effective user ID different from its real user ID does not produce a core image. The file contains sufficient information to determine what the process was doing at the time of its termination. Core file contents con- sist of objects that represent different segments of a process. Each object is preceded by a data structure, and each data structure describes the corresponding object following it. The structure is defined in and includes the following members: The space and addr members specify the virtual memory address in the process where the described object began. The len member is the length of the object in bytes. The following possible values for type are defined in Process data as it existed at the time the core image was created. This includes initialized data, uninitialized data, and the heap at the time the core image is generated. A compiler-dependent data structure containing the exec data structure, the magic number of the executable file, and the command (see the declaration of the structure in The version number of the core format produced. This number changes with each HP-UX release where the core format itself has changed. However, it does not neces- sarily change with every HP-UX release. can thus be easily used by core-reading tools to determine whether they are compatible with a given core image. This type is expressed by a four-byte binary integer. The null-terminated version string associated with the kernel at the time the core image was generated. An architecture-dependent data structure containing per-process information such as hardware register contents. See the declaration of the structure in Process stack contents at the time the core image was created. Objects dumped in a image file are not arranged in any particular order. Use information to determine the type of the object that immedi- ately follows it. SEE ALSO
adb(1), coreadm(1M), coreadm(2), setuid(2), crt0(3), end(3C), signal(5). core(4)