On Tue, Jul 21, 2009 at 7:48 PM, Moinak Ghosh<moinakg at belenix.org> wrote:
> On Sun, Jul 19, 2009 at 1:07 PM, Moinak Ghosh<moinakg at belenix.org> wrote:
>> Hi Folks,
>>
>> ? I have been quiet for a while while busy building KDE 4 and it's
>> tanker-loads of dependencies. I am happy to mention that the entire
> [...]>
>> Dolphin crashes whenever I hover the mouse over a file icon. It appears
>> to be a font issue when trying to render the popup file preview box. This
>> essentially renders dolphin unusable right now.
>>
> [...]
>
> ? Okay so dolphin is now peaceful again. I was able to fix the crash.
> ? It turned out to be some C++ mumbo jumbo (I hate C++ soooo much)

Amen!

nuff said.

~b

> ? in Strigi Not KDEBase. Strigi is a desktop search helper consisting of
> ? a daemon and libraries: http://strigi.sourceforge.net/
>
> ? This is used by KDE 4. In one function strigi walks through an
> ? std::vector of the PATH components to locate a given utility. Once
> ? found it returns the std:string object of the fully resolved path. For some
> ? reason it was crashing when trying to return an std:string object local
> ? to the function to the caller where it gets assigned to another string
> ? variable. It was crashing inside
> ? libstdc++.so.6.0.11`__gnu_cxx::__exchange_and_add
> ? Googling revealed this Gentoo bug report:
> ? http://bugs.gentoo.org/228367
>
> ? However eventually I fixed the problem by resorting to dynamic allocation
> ? and passing pointers around. The patch is fairly simple:
> ? 
> http://belenix.svn.sourceforge.net/viewvc/belenix/trunk/spec_files/kde4/patches/strigi-04-path_assign_crash.diff?revision=339&view=markup
>
> ? Another point is that if you want a meaningful core file from a KDE app
> ? you need to run it with ?the options '--nofork --nocrashhandler' to run
> ? as foreground and disable the DrKonqui crash handler. Otherwise all
> ? you get is a vomit!
>
> Regards,
> Moinak.
> --
> ================================
> http://www.belenix.org/
> http://moinakg.wordpress.com/
> _______________________________________________
> belenix-discuss mailing list
> http://mail.opensolaris.org/mailman/listinfo/belenix-discuss
> http://groups.google.com/group/belenix-discuss
>

Reply via email to