plcrash_log_writer_write() currently only supports writing a crash log in which
the current thread is the crashed thread, executing on a signal handler.
To support Mach exception handlers, as well as generating a 'live' report for
any thread, we should update this function to support writing out -any- Mach
thread as the 'crashed' thread. This will require that the user specify a
ucontext_t for the *current* thread, rather than the crashed thread.
Original issue reported on code.google.com by landon.j.fuller@gmail.com on 5 Jan 2013 at 2:53
Original issue reported on code.google.com by
landon.j.fuller@gmail.com
on 5 Jan 2013 at 2:53