From kde-core-devel  Thu Jan 05 05:09:52 2006
From: Waldo Bastian <bastian () kde ! org>
Date: Thu, 05 Jan 2006 05:09:52 +0000
To: kde-core-devel
Subject: Re: KDE/kdebase/kicker/kicker
Message-Id: <200601042109.58834.bastian () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113643812219771
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart6248202.iJnLPN6KxX"

--nextPart6248202.iJnLPN6KxX
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

> > > In practice, even with identical versions of GCC, you'd find that many
> > > Linux distributions break the libstdc++ ABI.
> >
> > Please be specific. Which distribution did break the ABI when and with
> > which version of GCC?
>
> Debian and derivatives (some of which have since resolved this), Gentoo,
> and potentially --- I did not have direct testing access to any of those,
> so this is indirect based on googling of diffs --- some of RH/Fedora
> systems, for some periods of time (likely to be reverted now). GCC version
> is 4.0.x. The issue is use of an incompatible default allocator for the
> STL, which implies that if two dynamically linked objects were built on
> systems with and w/o a change, and they pass an STL container around (think
> of a function returning a vector --- aRts has those), destruction will
> crash.
> Mandriva and SUSE are compatible with FSF GCC.

Nasty. Thanks for providing the specifics.

Cheers,
Waldo

--nextPart6248202.iJnLPN6KxX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDvKomN4pvrENfboIRAgwkAJ9QMyyZUXqqdqo/g1QK+jD5DG/UpACfSG0s
nxMM2Aeok/jblxYNwU0omZo=
=8ebI
-----END PGP SIGNATURE-----

--nextPart6248202.iJnLPN6KxX--