Development/Tutorials/Debugging/Using Error Messages - Revision history

AnneW at 12:44, 13 July 2012

2012-07-13T12:44:57Z

Icwiener: Fix syntax highlighting.

2011-06-27T15:43:40Z

Fix syntax highlighting.

Rakuco: /* Links */ Fix capitalization typo

2009-06-25T20:08:29Z

‎Links: Fix capitalization typo

Powerfox: /* Links */

2008-08-28T13:08:51Z

‎Links

Powerfox: /* Links */ Note about kdebug.areas

2008-08-28T13:08:11Z

‎Links: Note about kdebug.areas

Tampakrap: fixed small html typo :)

2008-02-04T19:53:25Z

fixed small html typo :)

DrSlowDecay: +Language navigation

2008-01-16T16:15:10Z

+Language navigation

Dhaumann: adept to new kdebug

2007-09-22T09:13:54Z

adept to new kdebug

Jstaniek at 13:50, 14 June 2007

2007-06-14T13:50:23Z

Jstaniek: /* Links */

2007-06-14T13:48:08Z

‎Links

← Older revision		Revision as of 12:44, 13 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language_Navigation_Bar\|Development/Tutorials/Debugging/Using Error Messages}}~~	+

	When you start a konsole and type the commands to start an application you		When you start a konsole and type the commands to start an application you

@@ Line 7: / Line 7: @@
 compiled with the debugging enabled. So using a precompiled package from a distribution
 probably will not give you this information. If you compiled the application
-yourself, make sure the configure option "<tt>--disable-debug</tt>" was not used.
+yourself, make sure the configure option <tt>--disable-debug</tt> was not used.
 In KDE all debugging text-output can be switched on or off based on so
@@ Line 15: / Line 15: @@
 When you are debugging it is best to simply start a konsole and start the
 application from there. In a konsole you could simply type:
+<pre>
- kicker
+kicker
+</pre>
 and in the konsole kicker could return a message like:
+<pre>
- ERROR: kicker is already running!
+ERROR: kicker is already running!
+</pre>
 When a lot of output is written to the konsole it might go out of view before
 you could read it, therefor it is easy to create a text file which contains
 all this information, to do so type the following:
+<pre>
- application 2&gt;&amp;1 | tee debug.log
+application 2&gt;&amp;1 | tee debug.log
+</pre>
 where 'application' can be replaced with the application you are debugging.
 Afterwards you could open the file 'debug.log' to look at the messages again.
@@ Line 39: / Line 39: @@
 not just the application you are debugging!
-'''Case 1: Graphical login (i.e. kdm, gdm, xdm, etc.'''
+'''Case 1: Graphical login (i.e. kdm, gdm, xdm, etc.)'''
 The debug messages get redirected into the file {{path|~/.xsession-errors}} or
@@ Line 56: / Line 56: @@
 The debug messages are usually printed in C++ with the kDebug or kWarning statement. Example:
+<pre>
- kDebug(1210) << "arbitrary message";
+kDebug(1210) << "arbitrary message";
- kWarning(1210) << "this rather should not happen";
+kWarning(1210) << "this rather should not happen";
+</pre>
 The number 1210 (so called ''debug area'') in this case represents kicker.  You can omit the number.

@@ Line 63: / Line 63: @@
 See also: [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__kdebug.html kDebug/kWarning API documentation] and [http://websvn.kde.org/trunk/KDE/kdelibs/kdecore/kdebug.areas?view=markup kdebug.areas] for list of debug areas numbers.
-Note that you can use add_definition(-DKDE_DEFAULT_DEBUG_AREA=<number> ) in CmakeLists.txt to specify default debug area.
+Note that you can use ''add_definition(-DKDE_DEFAULT_DEBUG_AREA=<number>)'' in CMakeLists.txt to specify default debug area.
 ''Initial Author:'' [mailto:zander@kde.org Thomas Zander]

@@ Line 62: / Line 62: @@
 The number 1210 (so called ''debug area'') in this case represents kicker.  You can omit the number.
-See also: [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__kdebug.html kDebug/kWarning API documentation] and [http://websvn.kde.org/trunk/KDE/kdelibs/kdecore/kdebug.areas?view=markup] for list of debug areas numbers.
+See also: [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__kdebug.html kDebug/kWarning API documentation] and [http://websvn.kde.org/trunk/KDE/kdelibs/kdecore/kdebug.areas?view=markup kdebug.areas] for list of debug areas numbers.
 Note that you can use add_definition(-DKDE_DEFAULT_DEBUG_AREA=<number> ) in CmakeLists.txt to specify default debug area.
 ''Initial Author:'' [mailto:zander@kde.org Thomas Zander]

@@ Line 62: / Line 62: @@
 The number 1210 (so called ''debug area'') in this case represents kicker.  You can omit the number.
-See also: [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__kdebug.html kDebug/kWarning API documentation].
+See also: [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__kdebug.html kDebug/kWarning API documentation] and [http://websvn.kde.org/trunk/KDE/kdelibs/kdecore/kdebug.areas?view=markup] for list of debug areas numbers.
 ''Initial Author:'' [mailto:zander@kde.org Thomas Zander]

@@ Line 48: / Line 48: @@
 Use the following command to restart your session:
-  startx 2&gt;&amp;1 | tee startx.log</pre>
+  startx 2&gt;&amp;1 | tee startx.log
 so that all the debug messages of applications started at KDE's startup (and

← Older revision		Revision as of 16:15, 16 January 2008
Line 1:		Line 1:
		+	{{Template:I18n/Language_Navigation_Bar\|Development/Tutorials/Debugging/Using Error Messages}}
		+
	When you start a konsole and type the commands to start an application you		When you start a konsole and type the commands to start an application you
	will see all sorts of statements are printed in the konsole while the		will see all sorts of statements are printed in the konsole while the

@@ Line 8: / Line 8: @@
 In KDE all debugging text-output can be switched on or off based on so
-called 'sections'. One application can be one section. One part of the kde
+called '''areas'''. One application can be one or more area. One part of the kde base libraries can be another area. Enabling/disabling these areas from being printed can be done using the '''kdebugdialog''' application. For simple debugging selecting all
-base libraries can be another section.
-Enable/disabling these sections from being printed can be done using the
 '''kdebugdialog''' application. For simple debugging selecting all
 sections is probably wise.

@@ Line 61: / Line 61: @@
   kWarning(1210) << "this rather should not happen" << endl;
-The number 1210 (so called ''debug area'') in this case represents kicker.
+The number 1210 (so called ''debug area'') in this case represents kicker.  You can omit the number.
-Notes:
+See also: [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__kdebug.html kDebug/kWarning API documentation].
-* you can omit the number
-* you can control what debug areas are verbose using kdebugdialog program
-−
-* [http://api.kde.org/4.0-api/kdelibs-apidocs/kdecore/html/group__kdebug.html kDebug/kWarning API documentation]
 ''Initial Author:'' [mailto:zander@kde.org Thomas Zander]