Jump to content

Projects/KDE on Windows/Tools: Difference between revisions

From KDE Community Wiki
Rhabacker (talk | contribs)
m Add top level anchor
Rhabacker (talk | contribs)
add section "DebugView"
Line 24: Line 24:


Note: Normally KF5 applications use [https://community.kde.org/Projects/KDE_on_Windows/Getting_a_Backtrace_with_DrKonqi DrKonqi] to automatically generate a backtrace after a crash
Note: Normally KF5 applications use [https://community.kde.org/Projects/KDE_on_Windows/Getting_a_Backtrace_with_DrKonqi DrKonqi] to automatically generate a backtrace after a crash
= DebugView =
You can download DebugView from https://docs.microsoft.com/en-us/sysinternals/downloads/debugview.
To display debug messages, you must start this tool before the associated KDE application.

Revision as of 13:15, 11 February 2019

WinDbg

Download a binary with debug symbols

You must download a binary for the corresponding KDE applications with debug icon support from https://binary-factory.kde.org, e.g. https://binary-factory.kde.org/job/Umbrello_Nightly_win64/win64/.

  1. download umbrello-master-xxx-windows-msvc2017_64-cl.7z
  2. download umbrello-master-xxx-windows-msvc2017_64-cl-dbg.7z
  3. Unpack both archives to the same location.

Download a debugger

  1. Download SDK installer from https://developer.microsoft.com/de-de/windows/downloads/windows-10-sdk
  2. Start winsdksetzup, select "Download the Windows Software Development Kit ...." and press "Next".
  3. Uncheck all except "Debugging Tools for Windows x64".
  4. After the download is complete, enter the download directory and run "X64 Debuggers And Tools-x64_en-us.msi" from the Installers subdirectory.
  5. Then search the Start menu for "WinDbg (X64)" and run it.
  6. Select "File"->"Open Executable" from the application menu and select the main executable file you unpacked before, e.g. <unpack-root>\bin\umbrello5.exe.
  7. Select ""Debug"->"Go" to start the application. In case of a crash it will stop automatically.

Get the back trace

  1. Select "View"->"Processes and Threads" from the application menu and select the main thread (id 000) if not already selected.
  2. Select "View"->"Callstack" to see the backtrace.
  3. Press "Source" in the call stack windows to see the source information.
  4. To save the call stack to the clipboard, press the icon on the left side of the Close button in the window title.
  5. Open a new bugs at https://bugs.kde.org and paste the clipboard content into that bug.


Note: Normally KF5 applications use DrKonqi to automatically generate a backtrace after a crash

DebugView

You can download DebugView from https://docs.microsoft.com/en-us/sysinternals/downloads/debugview.

To display debug messages, you must start this tool before the associated KDE application.