Comment # 6 on bug 1017652 from Karl Ove Hufthammer

(In reply to Dominique Leuenberger from comment #4)
> The sad thing is that tracker is only suffering from underlying libs that
> generally crash.
> 
> So in any case, we need sample files that tracker tries to extract and
> fails. Then we can identify the library causing the failure and fix them
> directly

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?