Jump to content
TrinityCore

Leaderboard

Popular Content

Showing content with the highest reputation on 02/05/13 in Posts

  1. Don't be lazy, compile them yourself.
    1 point
  2. How to enable debug logs How i get good crashlogs under Linux? Under linux compile with the following flags: declare -x CFLAGS="-m64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O0 -g3 -ggdb3 -pipe -msse3 -fno-strength-reduce -fno-delete-null-pointer-checks -fno-strict-aliasing -frename-registers -rdynamic" declare -x CXXFLAGS="-m64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O0 -g3 -ggdb3 -pipe -msse3 -fno-strength-reduce -fno-delete-null-pointer-checks -fno-strict-aliasing -frename-registers -rdynamic" cmake ../ -DCMAKE_INSTALL_PREFIX=/change/path/to/trinity -DCMAKE_BUILD_TYPE=None If your core lags to much change -O0 by -Og or even -O1. Then copy TrinityCore/contrib/debugger/crashreport.gdb to your Trinitycore's bin directory and create a file with the following lines and make it runable: cp backtrace.log backtrace.`date +%Y%m%d-%H%M%S`.log screen -A -m -d -S tri_world gdb -x crashreport.gdb ./worldserver -c ../etc/worldserver.conf When your core crashes you will have a file called backtrace.log on your TrinityCore's directory. How i get good crashlogs under Windows? Select the dropdown on compile mode and change from RelWithDebug to Debug, Release mode crashlogs are useless.
    1 point
×
×
  • Create New...