D14606: KCrash: DrKonqi cancelled = able to start...

David Faure noreply at phabricator.kde.org
Sun Aug 5 17:18:12 BST 2018


dfaure added a comment.


  In D14606#303654 <https://phabricator.kde.org/D14606#303654>, @rjvbb wrote:
  
  > I think there is no way at this level of interaction to determine if an application crashed after start and distinguish that from something like a "user-cancelled" return code, or is there?
  
  
  There are some heuristics in kio's KProcessRunner, but aren't we getting completely sidetracked?
  Step 1 figuring out if (and why) you get a non-0 exit code, step 2 fixing the bug, and only then step 3 thinking about hypothetical situations (drkonqi crashing) that we might want to handle better.

REPOSITORY
  R285 KCrash

REVISION DETAIL
  https://phabricator.kde.org/D14606

To: rjvbb, #frameworks, sitter
Cc: dfaure, kde-frameworks-devel, michaelh, ngraham, bruns
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180805/bfa9c027/attachment.html>


More information about the Kde-frameworks-devel mailing list