42
edits
Difference between revisions of "Debugging ScummVM"
Jump to navigation
Jump to search
m
valgrind option is leak-check not leakcheck
(→Tips: Add links on Git Bisect and Event Recorder to Debugging Tips section.) |
m (valgrind option is leak-check not leakcheck) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 19: | Line 19: | ||
This is especially useful on embedded ports which usually lack the stdout console used currently for debug output as described above.<br> | This is especially useful on embedded ports which usually lack the stdout console used currently for debug output as described above.<br> | ||
<br> | <br> | ||
The key combination to activate the debug console is CTRL-d <br> | The key combination to activate the debug console is CTRL-Alt-d <br> | ||
(though this | (though users can change this by altering it's entry in the ScummVM Options Keymapper tab).<br> | ||
<br> | <br> | ||
The default console provides the following default commands :<br> | The default console provides the following default commands :<br> | ||
| Line 77: | Line 77: | ||
This can be invoked similar to gdb as <tt>valgrind ./scummvm</tt>. On Mac OS X, you will also want to pass the <tt>--dsymutil=yes</tt> argument so that you will get debug symbol information. | This can be invoked similar to gdb as <tt>valgrind ./scummvm</tt>. On Mac OS X, you will also want to pass the <tt>--dsymutil=yes</tt> argument so that you will get debug symbol information. | ||
By default, this will output memory access issues. If you want to do leak checking, you should invoke as <tt>valgrind -- | By default, this will output memory access issues. If you want to do leak checking, you should invoke as <tt>valgrind --leak-check=full ./scummvm</tt>. | ||
For further details, you should consult the relevant documentation of these tools on their web sites or manual pages. | For further details, you should consult the relevant documentation of these tools on their web sites or manual pages. | ||