diff options
Diffstat (limited to 'kioslave/DEBUG.howto')
| -rw-r--r-- | kioslave/DEBUG.howto | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/kioslave/DEBUG.howto b/kioslave/DEBUG.howto index 5275a26eb..d4873e021 100644 --- a/kioslave/DEBUG.howto +++ b/kioslave/DEBUG.howto @@ -4,8 +4,8 @@ How does an io-slave get started? ================================= Your application request 'klauncher' via DCOP 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. +not have an idle slave ready, it will ask tdeinit to start a new one. +tdeinit forks and dlopens the library that contains the io-slave. Then it calls kdemain() or, if that is not present, main() in the library. @@ -18,22 +18,22 @@ that slaves for a certain protocol are started in debug mode. E.g. to start all 'http' slaves in debug mode, you type: - KDE_SLAVE_DEBUG_WAIT=http kdeinit + KDE_SLAVE_DEBUG_WAIT=http tdeinit -This will restart 'kdeinit' and 'klauncher'. +This will restart 'tdeinit' and 'klauncher'. When your application now requests a http slave, the slave will be started -by kdeinit, but before it calls kdemain() (cq. main()) it will suspend the +by tdeinit, but before it calls kdemain() (cq. main()) it will suspend the slave by sending it a SIGSTOP signal. -In the terminal from which you started kdeinit you will get the following +In the terminal from which you started tdeinit you will get the following message: -kdeinit: Suspending process -kdeinit: 'gdb kdeinit 16779' to debug -kdeinit: 'kill -SIGCONT 16779' to continue +tdeinit: Suspending process +tdeinit: 'gdb tdeinit 16779' to debug +tdeinit: 'kill -SIGCONT 16779' to continue -You can now debug your slave by typing (or pasting) 'gdb kdeinit 16779' in +You can now debug your slave by typing (or pasting) 'gdb tdeinit 16779' in a terminal. If you don't want to debug a slave you can let it continue by sending it a SIGCONT by typing 'kill -SIGCONT 16779'. @@ -51,9 +51,9 @@ Debugging io-slaves with valgrind 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: - KDE_SLAVE_VALGRIND=https kdeinit + KDE_SLAVE_VALGRIND=https tdeinit -The valgrind output will appear as the stderr output of the kdeinit process. +The valgrind output will appear as the stderr output of the tdeinit process. The $VALGRIND_OPTS environment variable can be used to pass options to valgrind. If you want to use a different skin: @@ -83,7 +83,7 @@ kioslaverc: [SMB] DebugLevel=100 -This will print additional debug info to the stderr of your kdeinit process, +This will print additional debug info to the stderr of your tdeinit process, which typically ends up in ~/.X.err or ~/.xsession-errors Happy debugging. |