D15573: replace custom backtracing in SlaveBase with KCrash

[Harald Sitter]

sitter added a comment.


  I am somewhat indifferent. It certainly has caused some grief for various reasons in various places, so it stands to reason that it should go. Also since auto-init of kcrash is essentially not a thing for application code (what with link-as-needed being a common distro flag) it's possibly more consistent to move it's enabling to the individual slaves.
  
  OTOH the forced kcrashing did reveal a whole bunch of problems with the existing slaves. It's not all bad. Perhaps the way to go is to detangle kcrash from qtgui as a hard dep. As I recall it's only used for reinit-tech anyway, so hardly useful for the slave use-case. kcrashcore if you will ;) (I doubt we'd actually need a separate lib to accomplish it though)

REPOSITORY
  R241 KIO

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

To: sitter, dfaure
Cc: cfeck, kde-frameworks-devel, michaelh, ngraham, bruns
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20190107/1e973657/attachment.html>