araxiaonline/TrinityCore
3
0
Fork 0
mirror of https://github.com/araxiaonline/TrinityCore.git synced 2026-06-13 03:32:28 -04:00
Code Issues Packages Projects Releases Wiki Activity

Contrib: Add example GDB backtrace generator script and a small readme on how to use it - Note: DO read the README file before using.

Browse Source 
(Allows for semi-automated crashreporting on GDB/*nix-based platforms with proper information included).

--HG--
branch : trunk
This commit is contained in:
click
2010-09-19 18:11:03 +02:00
parent 907203fdd9
commit 54212cf387
2 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
contrib/debugger/README Normal file
View File

@@ -0,0 +1,13 @@
The included crashreport.gdb allows for semiautomated hunting of
crashes. The crashlog-file will be named backtrace.log and contains all
the commands required to partially automate a crashlog-creation with the
proper information.
Usage: gdb -x crashreport.gdb <executable file>
For creating an efficient backtrace, use -DCMAKE_BUILD_TYPE=Debug as a
parameter to CMake during configuration - this increases the filesize,
but includes all the needed information for a decent and efficient
crashreport.
-- Good luck, and happy crashhunting.

16
contrib/debugger/crashreport.gdb Normal file
View File

@@ -0,0 +1,16 @@
set logging overwrite on
set logging file backtrace.log
handle SIG33 pass nostop noprint
set pagination 0
run
set logging on
echo \n--- DEBUG: BACKTRACE FULL\n\n
backtrace full
echo \n--- DEBUG: INFO REGISTERS\n\n
info registers
echo \n--- DEBUG: CALLS (x/32i $pc)\n\n
x/32i $pc
echo \n--- DEBUG: THREAD APPLY ALL BACKTRACE\n
thread apply all backtrace
set logging off
quit