Building Sentry, a service to process native crash reports and minidumps

Debuggers — and also Sentry — are presented with the challenge of reading a stack trace from the threads’ call stack memory region, symbolicating them into human-readable function names, and, finally, enriching them with additional information. Unwind information indicates the size and contents of all function frame records so that the application or a debugger can walk the stack and extract values like the return address. And, this is essentially what debuggers do; they look up the respective instruction address in the debug file and then display all sorts of stored information.

Source: blog.sentry.io