[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Static initialisation crash in KGlobalSettings::generalFont()
From:       "David Jarvie" <lists () astrojar ! org ! uk>
Date:       2003-08-13 5:01:32
[Download RAW message or body]

A user has reported the following application crash in
KGlobalSettings::generalFont() during static initialisation. I presume that
the crash must be due to the order of static initialisation. Is this a fault
in kdelibs, or must such initialisations be done by an assignment at
runtime?

The line of code which presumably gives rise to the crash is:

const QFont
Preferences::default_messageFont(KGlobalSettings::generalFont().family(),
16, QFont::Bold);

The application was compiled on KDE from CVS (version 3.1.9 according to the
report) using gcc 3.3 on Linux 2.6.0.


#0 0x40a08df2 in KInstance::config() const () from 
/opt/kde/lib/libkdecore.so.4 
#1 0x40a00f24 in KGlobal::config() () from /opt/kde/lib/libkdecore.so.4 
#2 0x40a02e3d in KGlobalSettings::generalFont() () from 
/opt/kde/lib/libkdecore.so.4 
#3 0x080aa824 in __static_initialization_and_destruction_0 
(__initialize_p=1, __priority=65535) 
at preferences.cpp:38 
#4 0x080ab694 in _GLOBAL__I__ZNK11Preferences9classNameEv () at 
preferences.cpp:63 
#5 0x080e0255 in __do_global_ctors_aux () 
#6 0x0806ba3d in _init () 
#7 0x080e01cc in __libc_csu_init () 
#8 0x415ffc0b in __libc_start_main () from /lib/libc.so.6 

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]