TrustedUser
574
edits
Difference between revisions of "Debugging ScummVM"
Jump to navigation
Jump to search
→Tips: Add links on Git Bisect and Event Recorder to Debugging Tips section.
m (→Unix (Linux, Solaris, OSX, ...): cleanup) |
(→Tips: Add links on Git Bisect and Event Recorder to Debugging Tips section.) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 36: | Line 36: | ||
== Platform Specific Debugging == | == Platform Specific Debugging == | ||
Unlike the previous engine specific debugging output which is present in all builds including releases, debugging the platform backend code requires procedure and tools specific to the platform.<br> | |||
It also generally requires a debug build (either compiled yourself or a nightly build from [http://buildbot.scummvm.org/builds.html here]) as release builds are generally stripped of debugging symbols | |||
for reason of binary size.<br> | |||
If the observed bug only occurs on certain platforms or is unstable to reproduce, it is likely that the engine debugging output will not be sufficient, even with the possibility of adding further | |||
debug output and recompiling.<br> | |||
The following hints are provided for how to do low level debugging on various platforms. | |||
=== Android === | === Android === | ||
| Line 44: | Line 51: | ||
This should record any ScummVM related errors, warnings or other information, especially related to failures of the application to start or application crashes. | This should record any ScummVM related errors, warnings or other information, especially related to failures of the application to start or application crashes. | ||
For investigating user bug reports, it would useful to get this information, but the ADB requires a USB connection to a host PC with the ADK. | For investigating user bug reports, it would useful to get this information, but the ADB requires a USB connection to a host PC with the ADK. | ||
If you are using Android 4.1 or below (Android 4.2 requires root access to view logs), there is an easier to use log viewer application which runs on the device called "alogcat": | |||
[https://code.google.com/p/alogcat/]<br> | [https://code.google.com/p/alogcat/]<br> | ||
This requires no Host PC, USB connection or software setup beyond installing this app and can be downloaded from the Android Store (Google Play) for no cost. | This requires no Host PC, USB connection or software setup beyond installing this app and can be downloaded from the Android Store (Google Play) for no cost. | ||
=== Dreamcast === | |||
The debug builds with serial enabled from [http://buildbot.scummvm.org/snapshots/master/dc-serial-master-latest.tar.bz2 here] provide debug output to the Dreamcast serial port. | |||
With the appropriate cable to convert the 3V3 serial port to RS232 serial and a terminal program set to 57600 baud 8-N-1, you can view the debug output<br> | |||
from libronin, including the sbrk indication of remaining memory, which can be useful in diagnosing Out Of Memory crashes. | |||
=== Unix (Linux, Solaris, Mac OS X, MinGW ...) === | === Unix (Linux, Solaris, Mac OS X, MinGW ...) === | ||
| Line 74: | Line 88: | ||
command line option. | command line option. | ||
* Apart from using git [https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html bisect] to locate regressions, the (experimental) [[Event_Recorder|Event Recorder]] provides a framework for recording and replaying gameplay to detect regressions which may be useful. | |||