Difference between revisions of "Projects/KDE on Windows/Getting a Backtrace with DrKonqi"

Jump to: navigation, search
(Replaced content with "{{Moved To Community|Windows/Imported From TechBase/{{#titleparts:{{PAGENAME}}||3}}}}")
 
Line 1: Line 1:
=== Introduction ===
+
{{Moved To Community|Windows/Imported From TechBase/{{#titleparts:{{PAGENAME}}||3}}}}
With the advent of the KDE 4.7.0 release, it is possible to produce usable backtraces for Windows after experiencing a crash in a KDE application.
+
At the moment, the following description is only valid for the Microsoft compiler, if somebody could extend this to the MinGW compilers, I would be very glad.
+
 
+
=== Step by step ===
+
This assumes you have installed KDE with the kdewin-installer, selected the msvc2010 compiler and experience a crash in one of the KDE applications.
+
 
+
* rerun the installer and install all debug packages for (binary) packages you installed.
+
* for msvc2010 (Visual Studio compiler): set the environment variable _NT_SYMBOL_PATH to the location of your KDE installation. To do this, open a cmd.exe console window and type the following (replace "C:\Program Files (x86)\KDE-4.7.0" with the location where you installed KDE):
+
<pre>C:\Program Files (x86)\KDE-4.7.0> set _NT_SYMBOL_PATH="C:\Program Files (x86)\KDE-4.7.0"</pre>
+
* try to regenerate the crash by running the program from inside this console window:<pre>C:\Program Files (x86)\KDE-4.7.0> bin\kmymoney.exe</pre>
+
* copy the backtrace from DrKonqi into a file (save as a file currently crashes drkonqi itself) and append it to the bug report.
+
[[Category:MS Windows]]
+

Latest revision as of 14:13, 11 March 2016

This page is now on the community wiki.


This page was last modified on 11 March 2016, at 14:13. Content is available under Creative Commons License SA 4.0 unless otherwise noted.