	MidiVid Home
Main Page \| Class Hierarchy \| Class List \| File List \| Class Members \| File Members \| Related Pages

Bug Hunting

Bug Hunting: Tracking down problems

MidiVid GPU has a clever feature built in called an event log. When it starts up, the program checks for a file with the same name as the application, except with " log.txt" tacked on the end. If present, MidiVid GPU will open "MidVid GPU Log.txt" and start dumping information about what's going on as it does things. If you have a crash, or an incompatibility problem with a capture device or video card, this log file can help me track down the source.

It's a good idea to delete the file after you've tracked and reported a bug, because MidiVid GPU always appends new information to the existing file, so they can get big quickly.

Tips When Submitting Bugs

Try to make the problem happen again, and write down how you did it.
Try to isolate the problem down to the simplest thing you can do to cause it.
If you have a crash, or what could be a driver problem, create a "MidVid GPU Log.txt" file in the same folder as the application. Run the app as usual and cause the crash. The file will now contain information which could help me isolate the cause, so send it along.

Submit bugs or comments to mvbeta at jasondorie.com