Rebuilding aptitude did not work: The new binary died with a
core dump immediately.

This sounds strange. I just created a fresh chroot from the gcc-3.4
archive with debootstrap and aptitude seems to run fine from that.
How did you install? Could this be caused by mixing packages from the

gcc-3.3 and the gcc-3.4 archives? In this case maybe
'apt-get install --reinstall libsigc++-1.2-5c102' could help.

I did an upgrade from pure64. (A fresh installation did not
work for me, see my other EMail on this list.)
The suggested reinstall was not possible:
# apt-get install --reinstall libsigc++-1.2-5c102
Reading Package Lists... Done
Building Dependency Tree... Done
Reinstallation of libsigc++-1.2-5c102 is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
(The 2 packages not upgraded are libtiff4 and libtiff4-dev.)
But I could download it from
http://debian-amd64.alioth.debian.org/gcc-3.4/pool/unstable/main/amd64/libs/libsigc++-1.2/
and manually install it. Now the problem seems to be gone.
Why doesn't aptitude use libsigc++ 2.0?
Probably its unrelated, but when I tried to reinstall libsigc++
within aptitude I got an internal error saying
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x Apt errors x
xE: I wasn't able to locate file for the libsigc++-1.2-5c102 package. This might mean you need to manually fix this package. ax
xE: Internal error: couldn't generate list of packages to download ax
x [ Ok ] x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
Regards
Harri