MIPS pdata Format
The Microsoft Common Object File Format (COFF) specifies a pdata section that contains an array of function table entries for exception handling, and is pointed to by the exception table entry in the image data directory. The MIPS Calling Sequence Specification does not use this compressed pdata format, but instead supports _IMAGE_RUNTIME_FUNCTION_ENTRY as a structure to aid in stack walking at run time. The structure aids in debugging and exception processing. In most cases, MIPSII currently uses an uncompressed 20 bytes for each function for the _IMAGE_RUNTIME_FUNCTION_ENTRY entry. Leaf functions that do not have associated exception-handling routines do not have an associated pdata entry.
The data structure is a table, with one entry per function except for certain types of functions that do not need the pdata. The table is stored in a .pdata section.
The following table shows the function table entry format for MIPSII images.
| Offset | Size | Field | Description |
|---|---|---|---|
| 0 | 4 | Begin Address | Virtual address of the corresponding function. |
| 4 | 4 | End Address | Virtual address of the end of the function. |
| 8 | 4 | Exception Handler | Pointer to the exception handler to be executed. |
| 12 | 4 | Handler Data | Pointer to additional information to be passed to the handler. |
| 16 | 4 | Prolog End Address | Virtual address of the end of the function prolog. |
See Also
MIPS Prolog and Epilog | MIPS Epilog
Last updated on Thursday, April 08, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.