]>
Commit | Line | Data |
---|---|---|
55e3d2f6 A |
1 | .Dd November 7, 2008 |
2 | .Dt unwinddump 1 | |
3 | .Os Darwin | |
4 | .Sh NAME | |
5 | .Nm unwinddump | |
6 | .Nd "Displays compact unwind information in an executable" | |
7 | .Sh SYNOPSIS | |
8 | .Nm | |
9 | .Op Fl arch Ar arch-name | |
10 | .Ar file(s) | |
11 | .Sh DESCRIPTION | |
12 | When a C++ (or x86_64 Objective-C) exception is thrown, the runtime must unwind | |
13 | the stack looking for some function to catch the exception. Traditionally, | |
14 | the unwind information is stored in the __TEXT/__eh_frame section of each executable | |
15 | as Dwarf CFI (call frame information). Beginning in Mac OS X 10.6, the unwind | |
16 | information is also encoded in the __TEXT/__unwind_info section using a two-level | |
17 | lookup table of compact unwind encodings. | |
18 | .Pp | |
19 | The unwinddump tool displays the content of the __TEXT/__unwind_info section. | |
20 | .Sh SEE ALSO | |
21 | .Xr ld 1 | |
22 | .Xr dwarfdump 1 |