Create a trace log using `export KDE_FORK_SLAVES=true;With a Krusader that does not include the code of the present code review, execute:
export KDE_FORK_SLAVES=true; krusader -d
press the right arrow on an archive, and in the command line check that structured debug messages like
Pid:30112 ┏kio_krarcProtocol(147)
Pid:30112 ┗kio_krarcProtocol
Pid:30112 ┏stat(664)
Pid:30112 stat(665): /
Pid:30112 ┏setArcFile(877)
Pid:30112 setArcFile(878):
Pid:30112 ┗setArcFile
are *not* seen.
Build Krusader, execute `sudo make install`, etc. Execute:
export KDE_FORK_SLAVES=true; krusader -d
press the right arrow on an archive, and in the command line check that structured debug messages like
Pid:30112 ┏kio_krarcProtocol(147)
Pid:30112 ┗kio_krarcProtocol
Pid:30112 ┏stat(664)
Pid:30112 stat(665): /
Pid:30112 ┏setArcFile(877)
Pid:30112 setArcFile(878):
Pid:30112 ┗setArcFile
are seen, therefore showing a trace log.
Execute from the command line:
env KRDEBUG_BRIEF=true KDE_FORK_SLAVES=true krusader -d
press the right arrow on an archive, krusader -d` and then entering into compressed files.and see in the command line that structured debug messages like
┏kio_krarcProtocol
┗kio_krarcProtocol
┏stat
stat: /
┏setArcFile
setArcFile:
┗setArcFile
are seen, Add `KRDEBUG` linesnot showing information like process identifiers, add `KRFUNC` lines codeconsequently making trace logs more suitable to be compared with similar ones (for example the result of another experiment).
More advanced tests that I performed:
- Add `KRDEBUG` lines and `KRFUNC` lines to the code of Krusader, and also to the code of the iso and krarc kioslaves, compile and execute Krusader, and watch what is written to the trace log.
Create trace logs but using `env KRDEBUG_BRIEFEF=false KDE_FORK_SLAVES=true` previously, krusader -d` and compare those trace logs, etc.