История изменений

Olive has had built-in crash reporting for several months now, but some enhancements were made to make it even better. The crash report generated by Olive now serves as a complete backtrace in its own right, no longer requiring the use of debuggers like CDB, GDB, or WinDbg, or manually parsing the reports with symbols and stackwalking. This makes it a lot easier for developers to locate the cause of a crash, and potentially even gives advanced users an idea of what exactly caused the crash before it's even reported to us. Many bugs have already been fixed just from crash reports alone, so thanks to everyone who's been sending them in!

Сделано угадай на каком движке.

Olive has had built-in crash reporting for several months now, but some enhancements were made to make it even better. The crash report generated by Olive now serves as a complete backtrace in its own right, no longer requiring the use of debuggers like CDB, GDB, or WinDbg, or manually parsing the reports with symbols and stackwalking. This makes it a lot easier for developers to locate the cause of a crash, and potentially even gives advanced users an idea of what exactly caused the crash before it's even reported to us. Many bugs have already been fixed just from crash reports alone, so thanks to everyone who's been sending them in!

Сделано угадай на каком движке.

Olive has had built-in crash reporting for several months now, but some enhancements were made to make it even better. The crash report generated by Olive now serves as a complete backtrace in its own right, no longer requiring the use of debuggers like CDB, GDB, or WinDbg, or manually parsing the reports with symbols and stackwalking. This makes it a lot easier for developers to locate the cause of a crash, and potentially even gives advanced users an idea of what exactly caused the crash before it's even reported to us. Many bugs have already been fixed just from crash reports alone, so thanks to everyone who's been sending them in!