How to catch ScummVM crash errors

[bobdevis]

Ok, it seems we have a recurring problem. People do not know how to run ScummVM from the commandline so they have no idea how to catch those crash/abort/force-quit errors.
I thought I'd explain it in detail, once and for all.

1. Problem
Your ScummVM window 'disappears' when you do something and you have no idea why.

2. Solution
Check what the error messages are just before ScummVM stops working. Those error messages are clues to what went wrong.

2.1 Windows
a. Find and run a program called Command Prompt.
It should be at Start > Programs > Accessories > Command Prompt. The exact place may differ depending on your Windows version, so you may need to look around a bit.
b. Run ScummVM from the Command Prompt.
In most cases, copy-pasting the following block into the Command Prompt and pressing enter will do the trick;

Code: Select all

c:
cd ..
cd ..
cd ..
cd ..
cd Program Files
cd ScummVM
scummvm

However, if you didn't take the default installation options and installed ScummVM at a custom place, like D:\Stuff\Games\ScummVM, you will need differed commands, like;

Code: Select all

d:
cd ..
cd ..
cd ..
cd ..
cd stuff
cd games
cd scummvm
scummvm

c. Get the error messages.
When ScummVM stops working because of your problem, the Command Prompt window will still be there. It will have all the gory details about why ScummVM stopped.

2.2 OSX
a. Find and run a program called Terminal.
It should be in Finder > Applications > Utilities > Terminal.
The exact place might differ depending on your Mac OS version, so you may need to look around a bit.
b. Run ScummVM from the Terminal.
In most cases, copy-pasting the following line into the Terminal and pressing enter will do the trick;

Code: Select all

/Applications/ScummVM.app/Contents/MacOS/scummvm

If you somehow managed to install ScummVM somewhere else then /Applications/, you need to change this line accordingly.
c. Get the error messages.
When ScummVM stops working because of your problem, the Terminal window will still be there. It will have all the gory details about why ScummVM stopped.

2.3 Linux
a. Find and run a program called Terminal or Konsole.
The if you are a 'typical' Linux user, you are running Ubuntu. Then you can find the Terminal application like this; Ubuntu Button > Accessories > Terminal.
If you are using KDE, you can find Konsole like this; K-button > System > Konsole.
b. Run ScummVM from the Terminal.
In your Terminal/Konsole window, type

Code: Select all

scummvm

and press enter.
c. Get the error messages.
When ScummVM stops working because of your problem, the Terminal/Konsole window will still be there. It will have all the gory details about why ScummVM stopped.

3. Follow up
Ok, so now you have the errors that ScummVM gave you. With that info you can do the following things;
a. Try to fix it yourself.
Usually the errors will boil down to 'file not found' of 'file corrupt'. Try to re-copy the files that ScummVM is complaining about.
b. Search for the error.
You can use the errors as a search term in Google or in the ScummVM forum. It may get you somewhere.
c. Ask for help.
Start a help-me thread on this forum and post the error messages. Someone may know what is going wrong.

[sev]

Well, the more serious and much more recurring problem is people ignoring the documentation. Particularly this topic is fully covered in FAQ #5.6.


Eugene

[fingolfin]

Well, maybe we need to place the FAQ more prominently... (Do we include it with the binary, by the way? I hope we do...).

Also, bobdevis certainly gives more details. Maybe we can use his text to touch up FAQ 5.6 -- more details might help people (after we pointed them at it, at least