Main.BackTraces History
Hide minor edits - Show changes to markup
February 05, 2009, at 08:28 AM
by Stedevil --
Changed line 16 from:
gdb --args freedroidRPG -wqr1\\
to:
gdb --args freedroidRPG -wqr1\\
Changed line 18 from:
run\\
to:
run\\
Changed line 21 from:
bt full\\
to:
bt full\\
Added lines 23-24:
6) To exit from gdb type
quit\\
Changed line 39 from:
valgrind --tool=memcheck freedroidRPG -wqr1\\
to:
valgrind --tool=memcheck ./freedroidRPG -wqr0\\
Changed line 47 from:
valgrind --tool=callgrind --instr-atstart=no ./freedroidRPG -wqr1\\
to:
valgrind --tool=callgrind --instr-atstart=no ./freedroidRPG -wqr0\\
February 05, 2009, at 08:16 AM
by Stedevil -- Added link to old Windows instructions and small changes here and there
Added lines 9-12:
Changed line 15 from:
1) Run\\
to:
1) Start gdb:\\
Changed lines 17-18 from:
2) Type `run` to start the game\\
to:
2) To start the game type:
run\\
Changed lines 20-21 from:
4) Type "bt full"\\
to:
4) Type:
bt full\\
Changed lines 31-32 from:
valgrind is a memory utility that does profiling among other things
kcachegrind is the GUI for better visualisation of the results\\
to:
valgrind is a memory utility that does profiling among other things
kcachegrind is the GUI for better visualisation of the results\\
February 05, 2009, at 08:05 AM
by Stedevil --
Changed line 31 from:
valgrind --tool=memcheck freedroidRPG -wqr0\\
to:
valgrind --tool=memcheck freedroidRPG -wqr1\\
Changed line 39 from:
valgrind --tool=callgrind --instr-atstart=no ./freedroidRPG -wqr0\\
to:
valgrind --tool=callgrind --instr-atstart=no ./freedroidRPG -wqr1\\
February 05, 2009, at 08:04 AM
by Stedevil --
Changed line 12 from:
gdb --args freedroidRPG -wqr0\\
to:
gdb --args freedroidRPG -wqr1\\
Changed line 16 from:
5) Attach the output to the bug report or Email to the developer.\\
to:
5) Attach the output to the bug report or e-mail directly to the developer if they asked for that.\\
Changed line 33 from:
3) Send full output\\
to:
3) Attach the full output to the bug report or e-mail directly to the developer if they asked for that.\\
Changed line 45 from:
to:
7) Report the info somehow...
February 05, 2009, at 07:57 AM
by Stedevil --
Changed lines 13-16 from:
2) Reproduce crash.
3) Type "bt full"
4) Attach the output to the bug report or Email to the developer.\\
to:
2) Type `run` to start the game
3) Reproduce crash.
4) Type "bt full"
5) Attach the output to the bug report or Email to the developer.\\
February 05, 2009, at 07:55 AM
by Stedevil --
Changed line 9 from:
Install gdb if you dont already have them on your system.\\
to:
Install gdb if you dont already have it on your system.\\
Changed line 12 from:
gdb --args freedroidRPG -wq\\
to:
gdb --args freedroidRPG -wqr0\\
Changed line 24 from:
valgrind is a memory utility that does profiling among other things (the profiler is called callgrind)\\
to:
valgrind is a memory utility that does profiling among other things\\
Changed line 35 from:
Valgrind - profiling
to:
Valgrind - profiling (callgrind)
February 05, 2009, at 07:53 AM
by Stedevil -- Adding more details
Added lines 9-16:
Install gdb if you dont already have them on your system.
1) Run
gdb --args freedroidRPG -wq
2) Reproduce crash.
3) Type "bt full"
4) Attach the output to the bug report or Email to the developer.
\\
Added lines 21-23:
Install valgrind and kcachegrind if you dont already have them on your system.
\\
Changed lines 25-33 from:
kcachegrind is the GUI for better visualisation of the results
to:
kcachegrind is the GUI for better visualisation of the results
Valgrind - memcheck
1) Run
valgrind --tool=memcheck freedroidRPG -wqr0
2) Reproduce problem
3) Send full output
Added line 35:
Valgrind - profiling
Changed lines 37-43 from:
1) Install valgrind and kcachegrind if you dont already have them on your system.
2) Run
valgrind --tool=callgrind --instr-atstart=no ./freedroidRPG -wqr2
3) Get ready to reproduce the issue (eg load a savegame)
4) enable profiling my issuing "callgrind_control -i on" in another terminal
5) reproduce the problem
6) quit the game
7) start kcachegrind\\
to:
1) Run
valgrind --tool=callgrind --instr-atstart=no ./freedroidRPG -wqr0
2) Get ready to reproduce the issue (eg load a savegame)
3) enable profiling my issuing "callgrind_control -i on" in another terminal
4) reproduce the problem
5) quit the game
6) start kcachegrind\\
February 05, 2009, at 07:44 AM
by Stedevil --
Changed lines 1-26 from:
to:
Intro
To help out blablabla
GDB
Valgrind
valgrind is a memory utility that does profiling among other things (the profiler is called callgrind)
kcachegrind is the GUI for better visualisation of the results
1) Install valgrind and kcachegrind if you dont already have them on your system.
2) Run
valgrind --tool=callgrind --instr-atstart=no ./freedroidRPG -wqr2
3) Get ready to reproduce the issue (eg load a savegame)
4) enable profiling my issuing "callgrind_control -i on" in another terminal
5) reproduce the problem
6) quit the game
7) start kcachegrind
Report the info somehow
