On Sunday 19 January 2014 20:44:48 Kevin Ottens wrote: > What about KCRASH_NO_CRASH_HANDLER ? It's long but it makes it at least > descriptive.
Except that it's not technically correct, a crash handler (= a function called upon crashing) is still called, to handle autorestart functionality (when enabled by the app) and to print out some information (app foo is crashing). Or if the app installs a custom crash handler, it will be called. The only thing that this disables is drkonqi -- the command-line option has always been misnamed, although not as much as the env var :) KCRASH_DISABLE_DRKONQI is probably the only strictly-correct name. Anyhow, naming is the easy part.... on to actually implementing it... -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
