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

List:       kde-devel
Subject:    Re: Problems with KSycoca
From:       Waldo Bastian <bastian () kde ! org>
Date:       2003-08-27 21:12:11
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 27 August 2003 22:45, Ben Lamb wrote:
> > It seems to crash in a dynamic_cast function. Which compiler are you
> > using?  Did you recently switch compilers?
>
> gcc-3.2.2
>
> I knew there was something I should have mentioned :-)
>
> I've been used 3.2.2 for ages and is has been working fine. Might try
> recompiling everything with 3.3. I note 3.3.1 has just been released. Is
> there a recommended version?
>
> I also have gcc-3.3 kicking around but haven't used it for KDE.
>
> <thinks aloud>
> It's just possible that I might have accidentally compiled something with
> 3.3. Normally I'd expect linking errors as the name mangling would be
> different. However, isn't there now some kind of standardisation going on
> in this regard so that it will be possible to link things compiled with
> different c++ compilers?
> </thinks aloud>

The name mangling used by all gcc 3.x compilers is supposed to be the same I 
believe.

Can you add the following line to the KBuildSycoca::slotCreateEntry() function 
(after the { ):
	qWarning("KBuildSycoca::slotCreateEntry file = %s", file.latin1());

and then recompile & install? If you now run kbuildsycoca, does it print out 
one line only before it crashes or does it print a whole bunch of them? What 
is the last line that it prints?

Cheers,
Waldo
- -- 
bastian@kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/TR6rN4pvrENfboIRAjh4AJoC5pBk9dbTIB/SRjQJuSWU3BCN4ACfbIBp
E0+WGBE60/tLNxEfGf2VToA=
=1Te/
-----END PGP SIGNATURE-----
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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