2009/12/11 Michael Schuster <Michael.Schuster at sun.com>: > All, > > I'm seeing what looks somewhat like this: > https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/335155 with the > current bits available on http://solaris.bionicmutton.org:10001/ (I just > image-updated, so I'd assume I'm current). > > according to the bug report, this fix for issue was committed for KDE4.3 on > Apr. 30 - is there a way to find out whether we have this fix yet? if not, > is anyone aware of another issue where dolphin crashes upon start with > SIGSEGV and this stack trace (as reported by dbx): > > t at 1 (l at 1) program terminated by signal SEGV (no mapping at the fault > address) > 0xfb576d2f: unlock+0x002f: ? ? ?movl ? ? 0x0000000c(%esi),%edx > (dbx) where > current thread: t at 1 > =>[1] QMutex::unlock(0x811b729, 0x80473d0, 0xfb822cf0, 0x80ad14f), at > 0xfb576d2f > ?[2] QMutexLocker::~QMutexLocker(0x8047448, 0x0), at 0x80ad176 > ?[3] qRegisterResourceData(0x1, 0xfaea0274, 0xfaea02ba, 0xfaea0318, 0x0, > 0x0), at 0xfb6926f1 > ?[4] qInitResources_network(0xfae61838, 0xfae3c7b9, 0x80474bc, 0xfae3c926, > 0xfae61838, 0xfae3c909), at 0xfae3c791 > ?[5] __SLIP.INIT_A(0xfae61838, 0xfae3c909, 0x80474d0, 0xfae3ca27, > 0xfeffb804, 0xfa1c0094), at 0xfae3c7d6 > ?[6] __STATIC_CONSTRUCTOR(0xfeffb804, 0xfa1c0094, 0xfd150b68, 0x8047510, > 0xfefd13c6, 0xfa1c0098), at 0xfae3c926 > ?[7] __cplus_fini_at_exit(0xfa1c0098, 0xfeffb334, 0x1), at 0xfae3ca27 > ?[8] call_init(0xfa1c0018, 0x1, 0xfef903e0, 0x10), at 0xfefd13c6 > ?[9] setup(0x80477fc, 0x80478bc, 0x0, 0x8047fdf, 0x1000, 0xfefbf961, > 0xfefbc000, 0xfefbc000, 0xffffffff, 0x8050034, 0x8047fe5, 0x80477f4, > 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, 0x0, 0x2, 0x43dc6f, > 0xfefddf76), at 0xfefd02cb > ?[10] _setup(0x80477b0, 0x3fb28, 0x3, 0x80477f4, 0x4, 0x80477fc), at > 0xfefde278 > ?[11] _rt_boot(0x0, 0x804792c, 0x8047940, 0x804794b, 0x804795b, 0x804796f), > at 0xfefc4694
Hi, I'm afraid this is a different issue. There was a problem extremely similar to the dolphin one in nepomuk, which we (ade) were able to resolve by changing the order of linking libraries, see https://bugs.kde.org/show_bug.cgi?id=210822 I think the fix will be in the same spirit, but it'll need someone with C++/debugging/cmake skills & time. P. > > > thx > Michael > -- > Michael Schuster ? ? ? ?http://blogs.sun.com/recursion > Recursion, n.: see 'Recursion' > _______________________________________________ > kde-discuss mailing list > kde-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/kde-discuss >
