Comment # 7 on bug 1017652 from Dominique Leuenberger

(In reply to Karl Ove Hufthammer from comment #6)

> I���ll try to submit a sample file, but I don���t how to find out *which* files
> make the library crash. (Though I think there are many such files, since
> tracker-extract generates coredumps *countinously* if I don���t disable it.)
> 
> I have kept a few coredump files, but they are *huge* (e.g. several hundred
> MiB each). Are they of any use? How can I inspect them to figure out which
> file(s) caused the crashes?

Best is to extract a back trace directly on your machine; try with:

coredumpctl gdb /usr/lib/tracker-extract

then at the (gdb) prompt type "bt full"; if there are mentions of missing
-debuginfo packages, please install them and reproduce the coredumpctl gdb
command (there should be no '???' in the resulting dump.

With this it might be possible to find some clues where it's happening.