Development/Tutorials/Debugging/Debugging IOSlaves - Revision history

Reeves-87: /* Attaching gdb to an io-slave */ grammer correction

2012-06-25T16:39:53Z

‎Attaching gdb to an io-slave: grammer correction

Mire: /* GUI */ fixed apparent typo

2011-12-19T21:33:25Z

‎GUI: fixed apparent typo

Adawit: /* GUI */

2011-07-09T23:13:09Z

‎GUI

Adawit at 23:12, 9 July 2011

2011-07-09T23:12:40Z

Icwiener: Fix syntax highlighting.

2011-06-27T16:03:47Z

Fix syntax highlighting.

Adawit: /* How to get debug output */

2011-04-14T00:24:12Z

‎How to get debug output

Afiestas: yes, it is dbus now

2010-07-21T19:21:10Z

yes, it is dbus now

SadEagle: Give the proper skin name in the example

2010-05-31T20:47:02Z

Give the proper skin name in the example

Asn: /* specific kioslaves */

2010-05-19T16:03:52Z

‎specific kioslaves

Guy-kde: add a precision for the use of KDE_SLAVE_DEBUG_WAIT

2010-05-13T10:07:35Z

add a precision for the use of KDE_SLAVE_DEBUG_WAIT

@@ Line 24: / Line 24: @@
 </pre>
-For information, these commands don't work:
+For example, these commands don't work:
 <pre>
 KDE_SLAVE_DEBUG_WAIT=imap4 kdeinit4

@@ Line 73: / Line 73: @@
 # Press ALT+F2.
-# Enter 'debugdialog --fullmode' without the quotes and press enter.
+# Enter 'kdebugdialog --fullmode' without the quotes and press enter.
 # Select the desired number in the "Debug area", e.g. 7103 for http.
 # In the [Information] box, select "File" as the output.

@@ Line 74: / Line 74: @@
 # Press ALT+F2.
 # Enter 'debugdialog --fullmode' without the quotes and press enter.
-# Select the desired number in the "Debug area", e.g. 7103,7113 for http.
+# Select the desired number in the "Debug area", e.g. 7103 for http.
 # In the [Information] box, select "File" as the output.
-# Enter the desired file name, e.g. such as /tmp/kio_http.log.
+# Enter the desired file name, e.g. /tmp/kio_http.log.
 # Press OK to close the dialog.
 # Press ALT+F2, type ''kdeinit4'' and press enter or alternatively log out of KDE and log back in.
 ===Manual===

@@ Line 78: / Line 78: @@
 # Enter the desired file name, e.g. such as /tmp/kio_http.log.
 # Press OK to close the dialog.
-# Press ALT+F2, enter "kdeinit4" and press enter or alternatively log out and log back into your KDE session.
+# Press ALT+F2, type ''kdeinit4'' and press enter or alternatively log out of KDE and log back in.

@@ Line 12: / Line 12: @@
 E.g. to start all 'http' slaves in debug mode, you type:
+<pre>
-        in KDE 3: KDE_SLAVE_DEBUG_WAIT=http kdeinit
+KDE_SLAVE_DEBUG_WAIT=http kdeinit4
-        in KDE 4: KDE_SLAVE_DEBUG_WAIT=http kdeinit4
+</pre>
 This will restart 'kdeinit' and 'klauncher'.
@@ Line 20: / Line 20: @@
 Note:
 The string after the equal signal designates the name of a service, not the name of the slave! E.g. if you want to debug the kio_imap4, you must use:
-        KDE_SLAVE_DEBUG_WAIT=imap kdeinit4
+<pre>
 For information, these commands don't work:
-        KDE_SLAVE_DEBUG_WAIT=imap4 kdeinit4
+<pre>
-        KDE_SLAVE_DEBUG_WAIT=143 kdeinit4
+KDE_SLAVE_DEBUG_WAIT=imap4 kdeinit4
 When your application now requests a http slave, the slave will be started
@@ Line 32: / Line 36: @@
 In the terminal from which you started kdeinit you will get the following
 message:
+<pre>
 kdeinit: Suspending process
 kdeinit: 'gdb kdeinit 16779' to debug
 kdeinit: 'kill -SIGCONT 16779' to continue
 You can now debug your slave by typing (or pasting) 'gdb kdeinit 16779' in
@@ Line 53: / Line 58: @@
 KLauncher can be told to run certain io-slaves through valgrind. The following
 command can be used to let klauncher run all https io-slaves via valgrind:
+<pre>
-        KDE_SLAVE_VALGRIND=https kdeinit4
+KDE_SLAVE_VALGRIND=https kdeinit4
 The valgrind output will appear as the stderr output of the kdeinit process.
 The $VALGRIND_OPTS environment variable can be used to pass options to valgrind.
 If you want to use a different skin:
+<pre>
-        KDE_SLAVE_VALGRIND_SKIN=callgrind      ( for example )
+KDE_SLAVE_VALGRIND_SKIN=callgrind      ( for example )
+</pre>
 ==How to get debug output==
@@ Line 79: / Line 85: @@
 instead of stderr. E.g. I myself use the following lines in
 $KDEDIR/share/config/kdebugrc.
+<pre>
-       [7113]
+[7113]
-       InfoOutput=0
+InfoOutput=0
-       InfoFilename=/tmp/http
+InfoFilename=/tmp/http
-       [7103]
+[7103]
-       InfoOutput=0
+InfoOutput=0
-       InfoFilename=/tmp/http
+InfoFilename=/tmp/http
+</pre>
 This redirects all debug info for areas 7103 and 7113 (as used by kio_http)
 to the file /tmp/http.
@@ Line 92: / Line 98: @@
 To get debug information from the SMB slave you can add the following to
 kioslaverc:
+<pre>
 [SMB]
 DebugLevel=100
+</pre>
 This will print additional debug info to the stderr of your kdeinit process,
 which typically ends up in ~/.X.err or ~/.xsession-errors

@@ Line 3: / Line 3: @@
 ==How does an io-slave get started?==
-Your application requests 'klauncher' via DCOP [FIXME: Isn't that dbus now?] for a slave. If 'klauncher' does not have an idle slave ready, it will ask kdeinit to start a new one. kdeinit forks and dlopens the library that contains the io-slave.
+Your application requests 'klauncher' via DBus for a slave. If 'klauncher' does not have an idle slave ready, it will ask kdeinit to start a new one. kdeinit forks and dlopens the library that contains the io-slave.
 Then it calls a function called kdemain() in the library.

← Older revision		Revision as of 16:03, 19 May 2010
Line 88:		Line 88:
	== specific kioslaves ==		== specific kioslaves ==
	* [[Development/Tutorials/Debugging/Debugging IOSlaves/Debugging kio_fish\|kio_fish]]		* [[Development/Tutorials/Debugging/Debugging IOSlaves/Debugging kio_fish\|kio_fish]]
		+	* [[Development/Tutorials/Debugging/Debugging IOSlaves/Debugging kio_sftp\|kio_sftp]]

← Older revision		Revision as of 10:07, 13 May 2010
Line 17:		Line 17:

	This will restart 'kdeinit' and 'klauncher'.		This will restart 'kdeinit' and 'klauncher'.
		+
		+	Note:
		+	The string after the equal signal designates the name of a service, not the name of the slave! E.g. if you want to debug the kio_imap4, you must use:
		+	KDE_SLAVE_DEBUG_WAIT=imap kdeinit4
		+
		+	For information, these commands don't work:
		+	KDE_SLAVE_DEBUG_WAIT=imap4 kdeinit4
		+	KDE_SLAVE_DEBUG_WAIT=143 kdeinit4

	When your application now requests a http slave, the slave will be started		When your application now requests a http slave, the slave will be started