From 51670234e31b2e256d11fe065c43a7399131823c Mon Sep 17 00:00:00 2001 From: Moritz Bunkus Date: Sat, 12 Nov 2016 08:57:03 +0100 Subject: [PATCH] Created Debugging GUI startup problems (markdown) --- Debugging-GUI-startup-problems.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 Debugging-GUI-startup-problems.md diff --git a/Debugging-GUI-startup-problems.md b/Debugging-GUI-startup-problems.md new file mode 100644 index 0000000..b758306 --- /dev/null +++ b/Debugging-GUI-startup-problems.md @@ -0,0 +1,18 @@ +# Creating debug logs for GUI startup problems + +These are instructions for creating a debug log of the GUI startup procedure. I may ask you to follow these steps if you have problems running the GUI. + +Please do the following: + +• Download the [latest debug build](https://mkvtoolnix.download/windows/debug/) from the MKVToolNix website. +• Unpack it somewhere or install it, depending on which version you've downloaded +• Additionally download [Microsoft's DebugView utility](https://technet.microsoft.com/en-us/sysinternals/debugview.aspx). It's a small tool that doesn't even require installation, a single `.exe`. Save it somewhere. +• Start DebugView. Go to `File` → `Log to file`, select a file name to write the log messages to and close the dialog with `Ok`. +• Now start the debug build of MKVToolNix. In that moment the DebugView utility should show a couple of messages from the GUI. +• Close both programs and [send me](moritz@bunkus.org) the log file you've told DebugView to create. + +Thanks. + +You should keep DebugView around in case it's needed again. + +Categories: [debugging](FAQ#category-debugging) \ No newline at end of file