Re: [Tracker] tracker-extract goes south



Hi Philip

Am 28.06.2013 um 08:40 schrieb Philip Van Hoof <spam pvanhoof be>:
Did you enable either libstreamanalyzer support, or Qt support (for pixbuf extraction)? That's --enable-qt 
or --enable-libstreamanalyzer.

Those are if I recall correctly the only two reasons for extractor modules to link with C++ code for 
tracker-extract. It's of course possible that one of the libraries that tracker-extract's modules link with 
have a C API with a C++ implementation. I think poppler might be like that. In that case we should try to 
find out what the parameters where for this one:

 fdf51bfe g_module_open (807c206, 2, fdbe2698, fdbe9176) + 2cc
 fdbe91bd load_module (8097d04, 1, 0, fdbe94a2) + 55

(With gdb you could print them if you up to that location in the stack after the crash, you'll also need 
debugging symbols of GLib and tracker-extract for that).

as I've tried to explain in my last mail to Martyn, the problem is:

* libtracker-extract links with libexempi and libicui18n
* the opencsw package of libexempi links with stlport C++ standard library
* the opencsw package libicui18n links with Oracles C++ standard library libCstd

Linking with both stlport and libCstd results in undefined behavior, in this case it crashes in some 
initializer.

-Ralph

-- 
Ralph Böhme <rb netafp com>
Netatalk Developer | Support | Services
Curslacker Deich 254, 21039 Hamburg, Germany
http://www.netafp.com/

Attachment: smime.p7s
Description: S/MIME cryptographic signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]