--- Libc/Libc-1725.40.4/gen/backtrace.3
+++ Libc/Libc-583/gen/backtrace.3
@@ -26,15 +26,13 @@
 .\" SUCH DAMAGE.
 .\"
 .\"
-.Dd March 1, 2018
+.Dd February 15, 2007
 .Dt backtrace 3
-.Os "Darwin"
+.Os "Mac OS X"
 .Sh NAME
 .Nm backtrace ,
 .Nm backtrace_symbols ,
-.Nm backtrace_symbols_fd ,
-.Nm backtrace_image_offsets ,
-.Nm backtrace_from_fp
+.Nm backtrace_symbols_fd
 .Nd call stack backtrace and display functions
 .Sh SYNOPSIS
 .In execinfo.h
@@ -53,24 +51,6 @@
 .Fa "void* const* array"
 .Fa "int size"
 .Fa "int fd"
-.Fc
-.Ft void
-.Fo backtrace_image_offsets
-.Fa "void* const* array"
-.Fa "struct image_offset *image_offsets"
-.Fa "int size"
-.Fc
-.Ft int
-.Fo backtrace_from_fp
-.Fa "void* startfp"
-.Fa "void** array"
-.Fa "int size"
-.Fc
-.Ft size_t
-.Fo backtrace_async
-.Fa "void** array"
-.Fa "size_t size"
-.Fa "uint32_t* task_id"
 .Fc
 .Sh DESCRIPTION
 These routines provide a mechanism to examine the current thread's call stack.
@@ -104,42 +84,6 @@
 but the resulting strings are immediately written to the file descriptor
 .Fa fd ,
 and are not returned.
-.Pp
-.Fn backtrace_image_offsets
-attempts to transform a call stack obtained by
-.Fn backtrace
-into an array of image offsets, for deferred symbolication.  Each entry in the
-array has an offset relative to the
-.Li __TEXT
-section of the image with the given UUID.  The results are written to
-.Fa image_offsets
-which should be an array of
-.Fa size
-length.
-.Pp
-.Fn backtrace_from_fp
-takes a backtrace of frames starting from the given frame pointer.
-.Pp
-.Fn backtrace_async
-behaves exactly like
-.Fn backtrace
-unless it is invoked from a Swift async context.  In that case, instead of
-writing the return addresses of the OS call stack, the continuation addresses
-of the async invocations that led to the current state are provided.  If
-unwinding an async stack rather than an OS stack, the value pointed to by
-.Fa task_id
-will be set to a non-zero identifier that for the current process uniquely
-identifies the async task currently running.  Otherwise, 0 is stored.
-.Pp
-Note that the continuation addresses provided by
-.Fn backtrace_async
-have an offset of 1 added to them.  Most symbolication engines will substract
-1 from the call stack return addresses in order to symbolicate the call site
-rather than the return location.  With a Swift async continuation, substracting
-1 from its address would result in an address in a different function.  This
-offset allows the returned addresses to be handled correctly by most existing
-symbolication engines.
-.Pp
 .Sh EXAMPLE
 .Pp
     #include <execinfo.h>
@@ -155,17 +99,8 @@
     ...
 .Pp
 .Sh HISTORY
-.Fn backtrace ,
-.Fn backtrace_symbols ,
-and
-.Fn backtrace_symbols_fd
-first appeared in Mac OS X 10.5.
-.Fn backtrace_image_offsets
-and
-.Fn backtrace_from_fp
-first appeared macOS 10.14 and iOS 12.
-.Fn backtrace_async
-first appeared in macOS 12.
+These functions first appeared in
+Mac OS X 10.5.
 .Sh SEE ALSO
 .Xr dladdr 3 ,
 .Xr malloc 3