Guidelines and HOWTOs/Debugging/MS Windows: Difference between revisions

Revision as of 20:13, 28 August 2007

Warning

This section needs improvements: Please help us to

cleanup confusing sections and fix sections which contain a todo

Debuggind with DebugView

Debug messages generated by kDebug() and kWarning() are not unless application is compiled in so-called CONSOLE subsystem. To show these messages in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft).

→ More informations

Revision as of 20:13, 28 August 2007 view source Jstaniek (talk \| contribs) KDEDevelopers, spam-ninja, trusted 4,485 edits New page: {{improve}} ==Debuggind with DebugView== Debug messages generated by kDebug() and kWarning() are not unless application is compiled in so-called CONSOLE subsystem. To show these messages ...		Revision as of 20:13, 28 August 2007 view source Jstaniek (talk \| contribs) KDEDevelopers, spam-ninja, trusted 4,485 edits →Debuggind with DebugView Newer edit →
Line 4:		Line 4:
	Debug messages generated by kDebug() and kWarning() are not unless application is compiled in so-called CONSOLE subsystem. To show these messages in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft).		Debug messages generated by kDebug() and kWarning() are not unless application is compiled in so-called CONSOLE subsystem. To show these messages in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft).

	[http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx More informations].		→ [http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx More informations]