Bug#571170: marked as done (libstdc++.so.6: ELF load command address/offset not properly aligned)
Your message dated Sun, 28 Feb 2010 02:33:58 +0100
with message-id <4B89C806.7000902@debian.org>
and subject line fixed in 4.5-20100227-1
has caused the Debian Bug report #571169,
regarding libstdc++.so.6: ELF load command address/offset not properly aligned
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
571169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571169
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6
Version: 4.5-20100222-1
Severity: critical
File: libstdc++
Justification: breaks the whole system
I just updated libstdc++6 from experimental and this is the result when load-
ing any C++ program, after upgrade, include the entire APT suite:
apt-cache: error while loading shared libraries: libstdc++.so.6: ELF load
command address/offset not properly aligned
It makes my system unbootable. I've repaired the damage but others may not be
so lucky.
(Yes, I know it's experimental.)
-- System Information:
Debian Release: squeeze/sid
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libstdc++6 depends on:
ii gcc-4.5-base 4.5-20100222-1 The GNU Compiler Collection (base
ii libc6 2.11-0exp5 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.5-20100222-1 GCC support library
libstdc++6 recommends no packages.
libstdc++6 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.5-20100227-1
seems to be fixed, didn't investigate why ...
--- End Message ---
Reply to: