D10989: Check for nullptr in indexForNode

[Jaime Torres Amate]

jtamate added a comment.


  In D10989#219594 <https://phabricator.kde.org/D10989#219594>, @mpyne wrote:
  
  > I think valgrind has some flags you can use to try to generate a backtrace for where a freed block of memory was freed from, which might be useful for debugging.
  
  
  Thanks. The parameter is --read-var-info=yes, but it confirms my assumption, the job is already deleted and its space used by many others before the crash.
  With --tool=helgrind it shows more than 4.500 errors.
  With -tool=drd it shows more than 90.000 errors.
  Therefore I'll try to fix as many of them as possible, step by step, if it's possible.

REPOSITORY
  R241 KIO

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

To: jtamate, #frameworks, dfaure
Cc: mpyne, michaelh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180306/7b662108/attachment-0001.html>