[rkward] rkward: Properly init debugging (to terminal) before doing anything else.

Thomas Friedrichsmeier null at kde.org
Sat Oct 13 08:47:18 BST 2018

Git commit 213b8c0efdc1b1fbba59029cd244cbca47b3b77d by Thomas Friedrichsmeier.
Committed on 13/10/2018 at 07:45.
Pushed by tfry into branch 'master'.

Properly init debugging (to terminal) before doing anything else.

This fixes a crash on "rkward --help", triggered by a debug-message from the
new global static RKMessageCatalog::CatalogHash destructor.

M  +2    -1    rkward/main.cpp


diff --git a/rkward/main.cpp b/rkward/main.cpp
index 315ad1f1..9bab0702 100644
--- a/rkward/main.cpp
+++ b/rkward/main.cpp
@@ -119,7 +119,7 @@ QString findExeAtPath (const QString appname, const QString &path) {
 	return QString ();
-bool RK_Debug_Terminal = false;
+bool RK_Debug_Terminal = true;
 QMutex RK_Debug_Mutex;
 void RKDebugMessageOutput (QtMsgType type, const QMessageLogContext &ctx, const QString &msg) {
@@ -167,6 +167,7 @@ void RKDebug (int flags, int level, const char *fmt, ...) {
 int main (int argc, char *argv[]) {
+	RK_Debug::RK_Debug_Level = DL_WARNING;
 	QApplication app (argc, argv);
 	KCrash::setDrKonqiEnabled (true);

More information about the rkward-tracker mailing list