Bug 213480

Summary: dolphin crashes - library linking order ?
Product: [Applications] dolphin Reporter: tropikhajma <tropikhajma>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Solaris   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description tropikhajma 2009-11-06 22:44:10 UTC
Version:           4.3.73 (using Devel)
Compiler:          Sun Studio 12 U1 
OS:                Solaris
Installed from:    Compiled sources

dolphin crashes on startup. This is happening (I think) since kde 4.2.

The backtrace below is very similar to another crashing kde application that was tracked down to incorrect order of linking the libraries (https://bugs.kde.org/show_bug.cgi?id=210822)

(dbx) run
Running: dolphin 
(process id 22861)
t@1 (l@1) signal SEGV (no mapping at the fault address) in QMutex::unlock at 0xfb3f3cff
0xfb3f3cff: unlock+0x002f:	movl     0x0000000c(%esi),%edx
(dbx) where -l -v -h
current thread: t@1
=>[1] libQtCore.so.4.6.0:QMutex::unlock(0x8132fd9, 0xfb708204, 0x804741c, 0x80ac32f), at 0xfb3f3cff 
  [2] dolphin:QMutexLocker::~QMutexLocker(0x80474b0, 0x0), at 0x80ac356 
  [3] libQtCore.so.4.6.0:qRegisterResourceData(0x1, 0xfaac81f8, 0xfaac823e, 0xfaac829c, 0x0, 0x0), at 0xfb51f351 
  [4] libQtNetwork.so.4.6.0:qInitResources_network(0xfaa8419c, 0xfaa5da09, 0x8047524, 0xfaa5db76, 0xfaa8419c, 0xfaa5db59), at 0xfaa5d9e1 
  [5] libQtNetwork.so.4.6.0:__SLIP.INIT_A(0xfaa8419c, 0xfaa5db59, 0x8047538, 0xfaa5dc77, 0xfeffb804, 0xf9c400a0), at 0xfaa5da26 
  [6] libQtNetwork.so.4.6.0:__STATIC_CONSTRUCTOR(0xfeffb804, 0xf9c400a0, 0xfd2205e8, 0x8047578, 0xfefd13c6, 0xf9c400a4), at 0xfaa5db76 
  [7] libQtNetwork.so.4.6.0:__cplus_fini_at_exit(0xf9c400a4, 0xfeffb334, 0x1), at 0xfaa5dc77 
  [8] ld.so.1[L]:call_init(0xf9c40018, 0x1, 0xfef903e0, 0x10), at 0xfefd13c6 
  [9] ld.so.1[L]:setup(0x8047864, 0x804792c, 0x0, 0x8047fde, 0x1000, 0xfefbf961, 0xfefbc000, 0xfefbc000, 0xffffffff, 0x8050034, 0x8047fe4, 0x804785c, 0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff, 0x0, 0x2, 0x43dc6f, 0xfefde0a2), at 0xfefd02cb 
  [10] ld.so.1[L]:_setup(0x8047818, 0x3fb28, 0x3, 0x804785c, 0x4, 0x8047864), at 0xfefde3a4 
  [11] ld.so.1[L]:_rt_boot(0x0, 0x80479aa, 0x80479b7, 0x8047a15, 0x8047a2a, 0x8047ae8), at 0xfefc4694 
(dbx
Comment 1 tropikhajma 2009-12-22 16:15:07 UTC
the problem is not present with 4.3.80, I'll reopen if it reappears in 4.3.85