User Tools

Site Tools


Creating back-traces for debugging

Found a crash? Generate a back-trace so we can see exactly where Mixxx crashed.


  1. Download x64dbg, an open-source x64/x32 debugger for Windows that runs without installation from a folder and support the symbols file mixxx.pdb. (The alternative GDB for Windows is not able to read the pdb file)
  2. Extract the downloaded zip file into a folder of your choice. (When writing this we get
  3. Install Mixxx's debug symbol file:
    1. Re-install Mixxx 2.1 select “Change” and enable “PDB debug files”
  4. Copy the mixxx.pdb file from the mixxx install folder to the x64dbg symbols folder, create the folder if not exist
    1. 64 bit: %PROGRAMFILES%\Mixxx\mixxx.pdb → snapshot_2017-03-19_13-21\release\x64\symbols
    2. 32 bit: %PROGRAMFILES(x86)%\Mixxx\mixxx.pdb → snapshot_2017-03-19_13-21\release\x32\symbols
  5. Start x64dbg via double click on the bug icon of
    1. 64 bit: snapshot_2017-03-19_13-21\release\x64\x64dbg.exe
    2. 32 bit: snapshot_2017-03-19_13-21\release\x32\x32dbg.exe
  6. Load mixxx.exe: File → open → browse to Mixxx.exe (F3)
    1. 64 bit: %PROGRAMFILES%\Mixxx\mixxx.exe
    2. 32 bit: %PROGRAMFILES(x86)%\Mixxx\mixxx.exe
  7. Start and continue Mixxx: Debug → Run (F9) (three times)
  8. Make Mixxx crash.
  9. When it does, Go to the Call Stack View: View → Call Stack (Ctrl+K)
  10. Right Click: Copy → Full Table, To Log
  11. Go to the log: View → Log Window (Ctrl+L)
  12. Right Click: Copy

Linux & Mac OS X with Xcode 4.x

  1. From a command prompt/terminal, type “gdb mixxx” and press Enter.
    • OSX users need to specify the path for the executable file, e.g
      gdb /Applications/
    • Use the gdb “--args” option to pass arguments, e.g.
      gdb --args ./mixxx --controllerDebug --developer --resourcePath res

For all of the above

  1. When the gdb prompt appears, type set height 0 and press enter to disable screen paging.
  2. Type run and press enter.
  3. Make Mixxx crash. When it does, type the following into the gdb prompt: thread apply all bt. (There may be multiple pages of output. Make sure to hit <Enter> enough times to see it all.)
  4. To close the Mixxx window and end gdb, type the following into the gdb prompt: quit
  5. Copying the gdb info:
    • Windows users can copy the terminal buffer into a text file:
    1. Click the window's icon in the top left corner.
    2. Choose Edit–>Select All. Everything selected will be inverted (so black becomes white, white becomes black, etc) Note: a Windows console will not update while any part of it is selected.
    3. Press Enter to copy the selection to the clipboard and de-select everything.
    4. Paste the clipboard buffer into a Notepad text document.
    5. Attach that to a bug report. (See below.)
    • Linux/OSX users should be able to select terminal output by using the mouse, and then doing a right click and selecting Copy.
  6. Report a bug using the Mixxx bug reporting system on Launchpad. Bugs filed here are tracked by developers and will not fall through the cracks as easily as using the IRC channel or mixxx-devel. (If another bug matches your issue, please make a comment on that one including your system details instead of filing a new bug.) Make sure to attach your back-trace (click Add attachment or patch.) Do not paste it in the comment.
  7. If you do not want to use Launchpad, post the results in the forum, email them to mixxx-devel, or pastebin them and drop the link on Zulip or IRC. We'll then try to figure out where the crash is. Do not assume a developer will hear you in IRC, using a static system (bug tracker, e-mail, forum) is much preferred. The IRC channel is great for technical support though.

Note: To get a backtrace for a thread freeze you can do the same thing as above, but to get the gdb prompt, you have to press CTRL+Z in the terminal window to suspend Mixxx.

Mac OS X with Xcode 5.x

Apple switched to clang/lldb. Xcode 5 does not include the GNU compiler or tools.

  1. Open a terminal window.
  2. Specify the path for the executable file
    • lldb /Applications/
    • lldb output should read
      Current executable set to '/Applications/' (x86_64)
    • If want to pass flag-like arguments to Mixxx, you have to terminate the actual flags with “--”
      lldb -- ./mixxx --controllerDebug --developer --resourcePath res
  3. At the lldb prompt, type

    and press enter.

  4. Make Mixxx crash.
  5. When it does, type the following into the lldb prompt:
    thread backtrace all
  6. To close the Mixxx window and end lldb, type the following at the lldb prompt:
  7. Copy the lldb output. Select the terminal output by using the mouse, and then doing a right click and selecting Copy

For more informations, go to

Windows: creating a dump file

When reporting crashes on Windows in addition to the instructions above for creating a backtrace, it is extremely useful if you can provide a “dump” file. This contains important information about why Mixxx crashed and will help the development team find a fix.

To take a crash dump, follow these instructions:

  1. When Mixxx crashes, you'll see a dialog similar to the following:
  2. Do not click “Close the program”!
  3. Hit the keys “control”, “alt”, and “delete” on your keyboard at the same time and click “Start Task Manager” on the screen that follows.
    1. .
  4. Find mixxx.exe in the list of programs, right-click it and hit “Create Dump File”.
  5. The dump file will be located on your computer in %APPDATA%\..\Local\Temp\mixxx.dmp or similar.
    1. Tip: You can copy/paste %APPDATA%\..\Local\Temp\ into the start menu search box to open this folder.
  6. Upload mixxx.dmp (or whatever the file was called) to the bug report on the Mixxx bug reporting system on Launchpad.
  7. Important: Dump files must be matched to the exact version of Mixxx you are using. A dump file is useless if we do not know the exact build number of Mixxx you are using and whether Mixxx is 32-bit or 64-bit.
    1. To find the build number:
      1. See Help → About inside of Mixxx and look for gitXXXX.
      2. OR right-click mixxx.exe → Properties → Details → File Version and look for a number like 2.1.0.XXXX
    2. The easiest way to resolve all confusion is to provide us with the exact filename of the installer you used to install Mixxx (and the URL you downloaded it from if you know it). This will contain both the build number (gitXXXX) and whether the build is 32-bit or 64-bit.
Translations of this page:
creating_backtraces.txt · Last modified: 2018/11/05 18:06 by daschuer