Bug#932808: baloo-kf5: Upon start baloo crashes with Segmentation fault following upgrade to buster

[Bernhard Übelacker <bernhardu@mailbox.org>]

Control: tags -1 - moreinfo



Dear Maintainer,
I think the top frames with debug symbols would look like this:

    (gdb) bt
    #0  memcpy () in ?? () from /lib/x86_64-linux-gnu/libc.so.6
    #1  0x00007feaa926d05d in Baloo::PostingCodec::decode () at ./src/codecs/postingcodec.cpp:42
    #2  0x00007feaa925a679 in Baloo::PostingDB::get () at ./src/engine/postingdb.cpp:100
    #3  0x00007feaa926a8ca in Baloo::WriteTransaction::commit () at ./src/engine/writetransaction.cpp:275
    #4  0x00007feaa9260ea2 in Baloo::Transaction::commit () at ./src/engine/transaction.cpp:269
    ...

This seems to point to upstream bug report [1].

The return value of function e.g. mdb_get might
not be checked enough.

An attempt to solve this seems to be commit [2].

Kind regards,
Bernhard


[1] https://bugs.kde.org/show_bug.cgi?id=367480
[2] https://cgit.kde.org/baloo.git/commit/src/engine/postingdb.cpp?id=eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d