4688676f3e
Improve WheatyExceptionReport Windows crash report to write a cleaner and more readable crash report, in particular: - Fix missing variable Type in some cases - Fix missing variable Name in some cases - Properly format each member to avoid confusion when reading the log - Add support for double pointers, e.g. Type** - Add initial support for arrays, logging the number of elements and the first 10 elements for now. UDT members of array elements are not supported yet - Skip static members, SymTagVTable and other not needed types - Skip SymTagUDT with no children - Fix possible stack overflows when logging strings/char*/char[] values. - Fix "punting on symbol" error happening when trying to dereference bad pointers. - Fix <user defined> type being logged instead of the correct type when reaching WER_MAX_NESTING_LEVEL or with pointer types with invalid addresses.
TrinityCore
Introduction
TrinityCore is a MMORPG Framework based mostly in C++.
It is derived from MaNGOS, the Massive Network Game Object Server, and is based on the code of that project with extensive changes over time to optimize, improve and cleanup the codebase at the same time as improving the in-game mechanics and functionality.
It is completely open source; community involvement is highly encouraged.
If you wish to contribute ideas or code please visit our site linked below or make pull requests to our Github repository.
For further information on the TrinityCore project, please visit our project website at TrinityCore.org.
Requirements
- Platform: Linux, Windows or Mac
- Processor with SSE2 support
- ACE ≥ 5.8.3 (included for Windows)
- MySQL ≥ 5.1.0 (included for Windows)
- CMake ≥ 2.8.11.2 / 2.8.9 (Windows / Linux)
- OpenSSL ≥ 1.0.0
- GCC ≥ 4.7.2 (Linux only)
- MS Visual Studio ≥ 12 (2013) (Windows only)
Install
Detailed installation guides are available in the wiki for Windows, Linux and Mac OSX.
Reporting issues
Issues can be reported via the Github issue tracker.
Please take the time to review existing issues before submitting your own to prevent duplicates.
In addition, thoroughly read through the issue tracker guide to ensure your report contains the required information. Incorrect or poorly formed reports are wasteful and are subject to deletion.
Submitting fixes
Fixes are submitted as pull requests via Github. For more information on how to properly submit a pull request, read the how-to: maintain a remote fork.
Copyright
License: GPL 2.0
Read file COPYING
Authors & Contributors
Read file THANKS
Links
Documentation (powered by Doxygen)