https://bugs.kde.org/show_bug.cgi?id=421317
--- Comment #12 from Stefan Brüns <stefan.bru...@rwth-aachen.de> --- Git commit 819cb757b5742372cf017fba84955178c1f1a7d1 by Stefan Brüns. Committed on 14/11/2023 at 01:28. Pushed by bruns into branch 'master'. [ExtractorProcess] Handle signal mangling by DrKonqi DrKonqui catches the SIGSEGV or SIGILL from a misbehaving extractor, and then eventually quits the process. This may happen either by re-raising the signal, or just are regular `_exit(253)`. Which one is used depends on the kernel `/proc/sys/kernel/core_pattern` setting - if it uses a pipe, the signal will be reraised. The unexpected exit status was not handled before, and could cause a blocking indexer, as neither a `done()` or `failed()` signal would ever be emitted. This also causes the list of failed files to stay empty, i.e. `balooctl failed` would not return anything. M +1 -1 src/file/CMakeLists.txt M +12 -4 src/file/extractorprocess.cpp https://invent.kde.org/frameworks/baloo/-/commit/819cb757b5742372cf017fba84955178c1f1a7d1 -- You are receiving this mail because: You are watching all bug changes.
