Difference between revisions of "Debugging"

From Mumble Wiki
Jump to: navigation, search
m
Line 20: Line 20:
  
 
When you come to the bug or error that you saw in Mumble and the log stops displaying any more data, press Ctrl+N and in the input box put "~* kp" and press enter. If Mumble ''does'' crash then you can just run "~* kp" from the same window that the first log is in; where you see "0 : 000>" at the bottom left of the window put in the command and press enter.
 
When you come to the bug or error that you saw in Mumble and the log stops displaying any more data, press Ctrl+N and in the input box put "~* kp" and press enter. If Mumble ''does'' crash then you can just run "~* kp" from the same window that the first log is in; where you see "0 : 000>" at the bottom left of the window put in the command and press enter.
copy and paste the logs from the executable window and the window that says "Command:" next to the input box (if this step was needed) into two separate pastebins (http://pastebin.com/) and give the links to a developer. The developer can hopefully look over these logs and get clues to what the bug or error might be.
+
Copy and paste the logs from the executable window and the window that says "Command:" next to the input box (if this step was needed) into two separate pastebins (http://pastebin.com/) and give the links to a developer. The developer can hopefully look over these logs and get clues to what the bug or error might be.

Revision as of 22:40, 11 February 2009

Mumble Debugging

If you have a problem with Mumble and wish to help the developers in fixing it, it usually helps to give Mumble developers a debug log of what Mumble was doing before it crashed/had a bug. For this purpose of debug logging, there is WinDbg.

Running WinDbg

Download WinDbg (32 bit) or WinDbg (64 bit).

Now install with all the default options but click "Complete" when it comes to the installation type.

If you are on Windows Vista type "windbg" into the start menu search box and press enter. If you are on Windows XP click Start -> All Programs -> Debugging Tools for Windows (x86) -> WinDbg.

Now WinDbg should be running. Press Ctrl+E and in the window that pops up navigate to "mumble.exe", click it, then click "Open".

Mumble should now start to load. Whenever you see a line containing "int 3" just keep pressing F5 until Mumble completely starts and is functional (providing that it actually starts without crashing).

When you come to the bug or error that you saw in Mumble and the log stops displaying any more data, press Ctrl+N and in the input box put "~* kp" and press enter. If Mumble does crash then you can just run "~* kp" from the same window that the first log is in; where you see "0 : 000>" at the bottom left of the window put in the command and press enter. Copy and paste the logs from the executable window and the window that says "Command:" next to the input box (if this step was needed) into two separate pastebins (http://pastebin.com/) and give the links to a developer. The developer can hopefully look over these logs and get clues to what the bug or error might be.