Projects/KDE on Windows/Tools - Revision history

AnneW at 10:54, 15 July 2012

2012-07-15T10:54:11Z

2012-01-19T12:08:44Z

‎DebugView: Updated URL to Microsoft's webpage on DebugView

2010-01-24T13:27:57Z

2008-09-07T22:12:01Z

‎More System Diagnostics Tools

2008-09-07T22:11:19Z

‎More Diagnostics Tools

2008-09-07T22:08:23Z

‎Process Monitor

2008-09-07T22:02:32Z

autoruns

2008-03-27T20:43:53Z

‎Debugging Tools for Windows

2008-03-11T15:31:51Z

‎WinDbg

2008-03-11T15:28:04Z

‎WinDbg

← Older revision		Revision as of 10:54, 15 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Projects/KDE on Windows/Tools}}~~	+
	Required or recommended tools for development and using KDE libraries and applications under MS Windows.		Required or recommended tools for development and using KDE libraries and applications under MS Windows.

@@ Line 56: / Line 56: @@
 == DebugView ==
-Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool. The tool offers searching in logs, filtering them using wildcards and saving them to file. (freeware) [http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx more]
+Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool. The tool offers searching in logs, filtering them using wildcards and saving them to file. (freeware) [http://technet.microsoft.com/en-us/sysinternals/bb896647 more]
 [[Image:DebugViewWindows.png|thumb|center|DebugView window]]

← Older revision		Revision as of 13:27, 24 January 2010
Line 1:		Line 1:
		+	{{Template:I18n/Language Navigation Bar\|Projects/KDE on Windows/Tools}}
	Required or recommended tools for development and using KDE libraries and applications under MS Windows.		Required or recommended tools for development and using KDE libraries and applications under MS Windows.

@@ Line 72: / Line 72: @@
 == More System Diagnostics Tools ==
-*[http://technet.microsoft.com/en-us/sysinternals/default.aspx File and Disk Utilities, Networking Utilities, Process Utilities, Security Utilities, System Information, Miscellaneous Utilities]
+*[http://technet.microsoft.com/en-us/sysinternals/default.aspx Windows Sysinternals: File and Disk Utilities, Networking Utilities, Process Utilities, Security Utilities, System Information, Miscellaneous Utilities]
 *[http://msdn2.microsoft.com/en-us/library/aa139733.aspx Debugging and Error Handling, Performance Monitoring, Performance Tools Kit, Error Reporting, Windows Events]

@@ Line 71: / Line 71: @@
 AutoRuns provides very comprehensive knowledge of auto-starting locations, shows what programs are configured to run during system bootup or login, and shows the entries in the order Windows processes them. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. [http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx more]
-== More Diagnostics Tools ==
+== More System Diagnostics Tools ==
-[http://msdn2.microsoft.com/en-us/library/aa139733.aspx Debugging and Error Handling, Performance Monitoring, Performance Tools Kit, Error Reporting, Windows Events] (MSDN).
+*[http://technet.microsoft.com/en-us/sysinternals/default.aspx File and Disk Utilities, Networking Utilities, Process Utilities, Security Utilities, System Information, Miscellaneous Utilities]

@@ Line 63: / Line 63: @@
 == Process Monitor ==
-Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity.
+Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. Use it to discover what process is using given files (very useful knowledge since Windows can block these files). [http://technet.microsoft.com/de-de/sysinternals/bb896645(en-us).aspx more]
 [http://technet.microsoft.com/de-de/sysinternals/bb896645(en-us).aspx more]
 == AutoRuns ==

@@ Line 12: / Line 12: @@
 == Debugging Tools for Windows ==
-You can use ''Debugging Tools for Windows'' package to debug drivers, applications, and services on systems with Windows NT kernel. (freeware) [http://www.microsoft.com/whdc/devtools/debugging/default.mspx more]
+You can use programs from ''Debugging Tools for Windows'' package to debug drivers, applications, and services on systems with Windows NT kernel. (freeware) [http://www.microsoft.com/whdc/devtools/debugging/default.mspx more]
 Among [http://msdn2.microsoft.com/en-us/library/cc267862.aspx others], ''Debugging Tools for Windows'' do contain:

@@ Line 21: / Line 21: @@
 Form [http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx]: ''"WinDbg provides source-level debugging through a graphical user interface and a text-based interface. WinDbg uses the Microsoft Visual Studio debug symbol formats for source-level debugging. It can access any public function's names and variables exposed by modules that were compiled with Codeview (.pdb) symbol files.
 WinDbg can view source code, set breakpoints, view variables (including C++ objects), stack traces, and memory. It includes a command window to issue a wide variety of commands not available through the drop-down menus. [..] It also allows you to remotely debug user-mode code."'',
 Resources related to WinDbg:

@@ Line 23: / Line 23: @@
 Resources related to WinDbg:
 * [http://software.rkuster.com/windbg/WinDBG_A_to_Z.pdf WinDbg. From A to Z! &nbsp; ] - Theory and examples (56 pages, 580 Kb)
 * [http://software.rkuster.com/windbg/printcmd.htm Common WinDbg Commands (Thematically Grouped)]