the PID check was racy, bonus points for not writing data at all to the
lock and not reading it meaning less disk I/O
oh, yes - by using O_CLOEXEC the lock is stale-safe
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
also not storing the host name because it serves no real purpose other than
being a possible source of problem (hostname change?), copyrighting it to
me because there is nothing relevant left of the original implementation
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
KDebug no longer proxies messages designated for the shell to the Katie
message handler because the Katie message handler has its own abort logic,
e.g. if QT_FATAL_WARNINGS is not empty or the message type is fatal abort()
would be called
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
also define KDEBINDIR for the tests as it turns out that running
the tests from test target in directory other than the top-level
one (e.g. make -C kdecore/ test) breaks the logic/expectaions in
some tests thus using the full paths to the test tools.
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
for compatibilty reasons automoc4 support is not removed but it
shall be in the future. automoc4 has not been maintained for a
while (last commit is from 2011) and the stable release is from
2009.
CMake version >= 2.8.6 provides the functionality for mocking so
I see no reason to not make use of it.
